Berlin wrapup

I’ve been a bit delayed in writing all this up. All in all the Developers’s Meetup in Berlin went very well.

Wednesday. The first day was a little rough (I was jetlagged for most of it anyway) I thought. The large groups didn’t work out terribly well and weren’t conducive to getting work done. Although we got a lot of stuff for Google Summer of Code discussed (sidebar: our 2010 projects have been announced. Congrats to the 6 awesome proposals we’re working with this year), there were a lot of other things we needed to talk about too and everyone who attended wasn’t necessarily interested in GSoC. Spent the rest of the day hacking, trying to beat jetlag, and hitting up “Fashion Meets Tech” with Andrew.

Thursday. I have to say the small group structure we adopted on day 2 worked incredibly, and I think we should continue to use that model from now on. Having small groups allowed really focused discussions on things that could really interest you. For example, I was able to work with some people in discussions regarding long-term planning for Bugzilla and Code Review or file metadata–subjects that don’t interest a lot of people–and was able to skip the sessions on OpenID or the Toolserver. It gave you a group of really interested people all very focused on the same task at hand. All of the sessions I attended were fantastic, but I’d like to summarize my two most productive ones below:

New-installer – I led this session in one of the upstairs room just after lunch on Thursday. I was a little hesitant to show it off in the state it’s in, but I have no regrets after doing so. Everyone really seemed to like where it was going, and I got a lot of solid feedback (most of it should be at [[mw:New-installer issues]], feel free to add items if something’s missing). Also began working with Siebrand on the localization aspects. The installer’s i18n has been split into its own file, loaded like an extension, and he completed the Dutch translation so we could start debugging. Roan also took the time to clean up the Javascript and jQueryify it. I think everyone liked it though :)

Organizational issues – On the first day we mainly talked about GSoC. The second day covered a lot of really important subjects such as bugtracking, code review, release management, the Mediawiki roadmap and volunteer outreach. It was largely a consensus over our known trouble spots and single points of failure. Our new CTO, Danese, informed the group that these issues are known and that specific plans are in place to fill these gaps (contingent on new budgets, et cetera). This is welcome news for a lot of us in Mediawiki/Wikimedia development. The notes of all this are on meta.

Friday. Friday was mostly spent bugsquashing and bouncing ideas off one another. And the day we all started getting very worried about a volcano from Iceland that we couldn’t pronounce. So a bug was filed (and quickly took a life of its own).

The next several days were spent booking and rebooking flights. Changing hotels. Searching for laundromats. Trying to find places for free or cheap wifi. The whole conference wasn’t there (luckily), but the group who were an awesome group of people who made being “stranded in Berlin” a more enjoyable experience. I got to eat great food and talk wikis and tech for days on end. I couldn’t ask to have been stuck with a better group of people. Bonded by our ‘travelupdate’ list and FlightRadar24.com, we managed to all stick it out in Berlin and keep the wikis running.

I’m glad I got to see some familiar faces, some faces I had not seen, and entirely new faces I didn’t know. I won’t be in Gdansk this summer for Wikimania, but hopefully we can manage to pull together the “East Coast Hackfest” for sometime this winter.

Packing for Berlin

I’ll be attending the Developer’s Workshop in Berlin next month. I’m looking forward to meeting some new faces and spending a few days neck deep in MediaWiki internals. I’ve got a couple of things I’m planning to bring with me that I think people will like.

IdeaTorrent

People keep kicking around the idea of using IdeaTorrent for tracking enhancements to MediaWiki. I’d like to give it a shot so I’m in the process of setting up an instance of it for the Wikimedia community to play with. Hoping to have this ready by Berlin (if their website will stop going down!).

New-installer

In whatever shape it’s in, I plan to show off the new-installer branch to MediaWiki. This is a huge overhaul of not only the installation process itself, but the backend supporting it. I’ve also managed to sneak a long-overdue schema abstraction in, which should help with database maintenance in the future. I would like to have this in a slightly more workable state by Berlin, but I’ll be showcasing what I have nonetheless.

Git Transition/Code Review/Bug Tracking

People like Git. Some people think we should move to Git and rid ourselves of Subversion. I’m of mixed opinions, but I’m always open to trying new things. I’ve been working with Ævar to get a working Git copy of our Subversion repository with all of the metadata intact (or as much as we can preserve). People also are looking at alternatives to using CodeReview/Bugzilla for our tracking systems for code and bugs/enhancements. I’m hoping to have an instance of Gerrit up and running by Berlin as well, so people can toy with that and see what they think.

Pushing to a release

It’s one of those wonderful times of the year, when we get to branch MediaWiki for a stable release. That’s right, MediaWiki v1.16 has been branched and a release candidate is underway. Those of you following MediaWiki–either as a Wikimedian or for your outside uses–know that 1.16 has been a long time coming. Code reviewing has finally caught up to trunk and it’s high time a release is put forth.

A lot has changed in 1.16 (for the brave, the full RELEASE-NOTES), and I’d like to hit on some of the major things here that I think need mention:

  • The Metadata editor ($wgUseMetadataEdit) has been split into a separate extension, MetadataEdit
  • Introduced CDB interface for high-performance constant data
  • Default output format is now HTML5 instead of XHTML 1.0 Transitional (see $wgHtml5)
  • Maintenance scripts got a lot of cleanup and reorganization, AdminSettings.php no longer required
  • New hooks
  • Major improvements in SQLite support
  • Test suite is now at least organized (will see more coming here in 1.17)
  • Many many other bug fixes and new features

Hopefully we’ll see a general update to the Wikimedia cluster coming in the very near future, meaning that non-critical bugfixes that have been “Fixed in SVN” will finally see production deployment. The first 1.16 release candidate will be coming soon as well, which I encourage those of you using MediaWiki to download and test it out for us. See what works, what needs tweaking and what’s downright broken. It’s a big release, so we’d like to get as much feedback as humanly possible.

Remember that all bugs goto Bugzilla (recently upgraded and restyled), and more information is always better than less.