Current Code Contributors: March 2017

Mar. 30th, 2017 02:22 am
[personal profile] kareila posting in [site community profile] dw_dev
Every few months, I run through [site community profile] changelog compiling a list of who has been contributing patches to our code repository, with the understanding that this is not a competition, or any sort of "high score" list. It's intended as a guide for casual developers, to discern not only our most prolific contributors, but also those who have contributed to the project most recently and therefore would be more likely to provide a timely, informed response to development questions. That is why the list is sorted by "Latest" instead of "Changes".

In general, one commit on Github equals one point in the "Changes" column, but fractional points are awarded for collaborative efforts — the most common example being a new S2 theme, where usually half credit is awarded to the theme author and the other half to the person who converts the theme into a code patch. Due to the nature of development, some changes are massive contributions of new code, and others are tiny tweaks; there is no correlation with the amount of effort involved. We are grateful to everyone who helps to improve Dreamwidth, in ways large or small.

I last compiled this list at the end of September. Since that time, we have not been graced with any new contributors, but we are pleased to welcome [staff profile] denise and [personal profile] fu back to active development after a long absence.

  #  User                      Changes     Latest
  1. denise                     417.08     Thu Mar 30 04:19:59 2017 UTC
  2. fu                         2168.5     Thu Mar 30 04:12:07 2017 UTC
  3. kareila                      1151     Tue Mar 21 16:56:21 2017 UTC
  4. alierak                        33     Wed Mar 15 13:41:33 2017 UTC
  5. mark                        563.5     Wed Feb 15 22:47:17 2017 UTC
  6. kaberett                     44.5     Mon Feb 13 18:53:52 2017 UTC
  7. momijizukamori             229.16     Sat Feb 11 17:08:28 2017 UTC
  8. srukle                          9     Sat Feb 04 00:09:02 2017 UTC
  9. woggy                          17     Thu Sep 29 22:26:43 2016 UTC
 10. onlyembers                    0.5     Thu Sep 29 19:58:05 2016 UTC

 11. pinterface                   15.5     Sat Sep 24 00:19:48 2016 UTC
 12. wohali                          1     Wed Aug 31 14:12:26 2016 UTC
 13. hotlevel4                      53     Fri Jul 15 22:39:55 2016 UTC
 14. phidari                         2     Sat Jun 18 21:14:12 2016 UTC
 15. cesy                        29.83     Sat Jun 18 15:28:34 2016 UTC
 16. chrisboyle                     15     Sun May 15 12:08:22 2016 UTC
 17. me_and                         36     Sun May 15 11:33:08 2016 UTC
 18. dfabulich                       1     Mon Apr 25 19:53:40 2016 UTC
 19. azurelunatic                    8     Mon Mar 28 05:54:30 2016 UTC
 20. sgsabbage                      17     Wed Feb 24 20:45:39 2016 UTC
The rest of the list... (159 total) )
[personal profile] brainwane posting in [site community profile] dw_dev
Those of you who love Open Source Bridge: it's going to be June 20-23, in Portland, Oregon. The call for session proposals closes in a few days, on 31 March. Last month Denise mentioned she hasn't yet decided whether to treat OSB 2017 as a "take Dreamwidth people to this conference" conference. But regardless, figured you might want to know.

Changes this year: a Community Organizer track during the Friday unconference, more extracurricular activities, and "a new track to explore how activists are using technology, how open source communities are supporting activists, and how other open source and activist communities intersect."

Presentations, panels, sets of lightning talks, workshops, or other session types are welcome.

Presentations can fit either a short- or long-form slot. Short-form presentations will receive a 45 minute session, and long-form will have 1 hour and 45 minutes. Pick the format that best fits the scope and style of your presentation.


[Call for proposals]

Update on the Dreamhack server

Mar. 24th, 2017 03:29 am
[personal profile] sophie posting in [site community profile] dw_dev
Hi all,

As you may know, about 2-3 weeks ago the Dreamhack server died. Since then, [staff profile] mark and I have been working on getting its replacement going, and updating a few things.

It should be ready to go in a few days, and I wanted to make a few notes for when it comes back up:
  • Firstly and most importantly, you'll need to re-apply for a Dreamhack if you want one, and you'll be set up as if you were a new user. Any changes that you pushed to GitHub will be available, but any other data you may have had will be gone - apologies for that.

  • I do still have email addresses for everybody who had an account when the server went down, and I'll send out a one-time email to everybody when the server is up to point them to this post. After that, the only people who will receive emails about Dreamhacks will be those who have applied for one.

  • The address you need to use to log into the server via SSH will be different from the Web address domain. The email you receive when applying for a Dreamhack will state this clearly.

  • The new server will have an increased quota. The earlier quota of 500MiB was enough at first, but since then the space taken by a base install of Dreamwidth has risen to 270MiB. In light of this, I've raised the quota to 750MiB.

  • You won't need to do a one-off compilation of the stylesheets and JavaScript any more unless you make changes to them - the new-user script will automatically do that for you, and your Dreamhack will have working CSS out of the box.

  • Each user will automatically get a test database called "test_dreamhack_<user>", accessible using the same database user and password as the main database. You'll still need to configure it properly yourself for now, but the installer will at least copy the required files to $LJHOME/ext/local/t for you to configure. Later on I'm hoping that it'll be possible to have it configured automatically.

  • The official email address to contact me has changed - you should now use my Dreamwidth email address (sophie at dreamwidth dot org). Automated emails will come from this address, so if you had the previous email whitelisted you may want to whitelist this new one instead.
Thanks for your patience with this - there's a lot that's been going on, but the new server should be ready to go very soon! Watch this space. :)

If you have any questions, please leave a comment! I'll answer any questions you might have.

Announcing the Shim review process

Mar. 21st, 2017 01:29 pm
[personal profile] mjg59
Shim has been hugely successful, to the point of being used by the majority of significant Linux distributions and many other third party products (even, apparently, Solaris). The aim was to ensure that it would remain possible to install free operating systems on UEFI Secure Boot platforms while still allowing machine owners to replace their bootloaders and kernels, and it's achieved this goal.

However, a legitimate criticism has been that there's very little transparency in Microsoft's signing process. Some people have waited for significant periods of time before being receiving a response. A large part of this is simply that demand has been greater than expected, and Microsoft aren't in the best position to review code that they didn't write in the first place.

To that end, we're adopting a new model. A mailing list has been created at shim-review@lists.freedesktop.org, and members of this list will review submissions and provide a recommendation to Microsoft on whether these should be signed or not. The current set of expectations around binaries to be signed documented here and the current process here - it is expected that this will evolve slightly as we get used to the process, and we'll provide a more formal set of documentation once things have settled down.

This is a new initiative and one that will probably take a little while to get working smoothly, but we hope it'll make it much easier to get signed releases of Shim out without compromising security in the process.

Buying a Utah teapot

Mar. 20th, 2017 01:38 pm
[personal profile] mjg59
The Utah teapot was one of the early 3D reference objects. It's canonically a Melitta but hasn't been part of their range in a long time, so I'd been watching Ebay in the hope of one turning up. Until last week, when I discovered that a company called Friesland had apparently bought a chunk of Melitta's range some years ago and sell the original teapot[1]. I've just ordered one, and am utterly unreasonably excited about this.

Update: Friesland have apparently always produced the Utah teapot, but were part of the Melitta group for some time - they didn't buy the range from Melitta.

[1] They have them in 0.35, 0.85 and 1.4 litre sizes. I believe (based on the measurements here) that the 1.4 litre one matches the Utah teapot.

Photobucket

Mar. 17th, 2017 02:41 pm
[staff profile] karzilla posting in [site community profile] dw_maintenance
Thanks to everyone who let us know that Photobucket images were not loading properly on some pages. The problem seemed to be mostly limited to HTTPS requests; Dreamwidth maintains a list of known high-traffic image sites that support HTTPS, so that our secure content proxy service doesn't cache them unnecessarily. Unfortunately Photobucket seems to have recently changed their site configuration such that HTTPS requests aren't being served as expected, and we've now taken it out of our list of "proxy-exempt" sites.

If you continue to have issues, make sure you're not using HTTPS Photobucket links. It's a bit counterintuitive, but if you use HTTP instead, it will be automatically transformed on our end to an HTTPS link that uses p.dreamwidth.org.

Hope that clears everything up for now! Let us know if it doesn't...