67[updated 1] unique committers contributed code to MediaWiki.
The total number of unreviewed commits went from about 100 to 138.
About 34 shell requests were processed.
63 developers got developer access to Git and Wikimedia Labs, of which 60 are volunteers.
Wikimedia Labs now hosts 81 projects, 136 instances and 305 users.
—Engineering metrics, Wikimedia blog
The Wikimedia Foundation's engineering report for April 2012 was published this week on the Wikimedia Techblog and on the MediaWiki wiki, giving an overview of all Foundation-sponsored technical operations in that month (as well as brief coverage of Wikimedia Deutschland's Wikidata project). Three of the headlines for the month have already received coverage in previous issues of the Signpost: the selection of nine Google Summer of Code students (explored in more detail below), the shift to a rapid deployment cycle with the deployment of 1.20wmf1 and a new version of the Wikimedia iOS app. Of the two others, one relates to work on a document detailing Wikimedia engineering’s goals for the next fiscal year, which will be featured in the "Technology report" as soon as it becomes official, and the deployment of a new mobile skin (example), which occurred after the publication of last week's issue. The skin update has since received broadly positive commentary among users; it provides a rival to the more native experience of an Android or iOS app.
Elsewhere, the roundup contained details of a massive improvement in the amount of time taken to use Wikimedia's Lucene-based internal search engine after "months of preparation and refactoring work". The difference reported was "quite amazing": the actual search component of 99% of search requests now takes under a second, down from nine seconds before; and the average search time is now 100 ms, down from 700 ms. Among the interesting updates included in the report was the news that the localisation team had started coding for a universal language selector, over 18 months after the feature was first proposed.
Coding has begun on a full system of Lua scripting, while April also saw over 20x improvements in the processing speed of the new parser on template heavy pages, suggesting that preparations for its rollout (a prerequisite for deployment of the new Visual Editor) will begin shortly. Among the relative failures of the month was the deployment of a new media caching layer ("Varnish"), which, while it has the potential to improve performance and scalability, seems to be preventing users from downloading large files successfully (bug #36577).
Not all fixes may have gone live to WMF sites at the time of writing; some may not be scheduled to go live for many weeks.
1.20wmf2 begins deployment process, 1.19 released: 1.20wmf2, the second "rapid deployment" to Wikimedia sites, began its process of deployment on April 30 when MediaWiki.org was switched over to the latest version, 20 days after the wiki received 1.20wmf1. It was then deployed to Wikimedia Commons May 2 2012, where it will have its greatest impact: the most significant feature of 1.20wmf2 is the introduction of so-called "chunked" uploads, which prevent intermittent connection failures from restarting an upload in its entirety. Representing just those 20 days of development, the deployment (which also hit the English Wikipedia on May 7 2012 and will be introduced to other Wikipedias on May 9 2012) includes some 47 bugfixes, among them fixes allowing the translation of edit notices and better display of the Vector skin on "high definition" devices. This week also saw the official release of MediaWiki 1.19 to external sites, allowing their wikis to benefit from a similar range of improvements as those that came to Wikimedia wikis in late February (wikitech-l mailing list).
Gerrit upgraded: Gerrit, MediaWiki's new code review system, has been upgraded to version 2.3, incorporating "lots of fixes and various other improvements". However, the most notable feature is the internalisation of Git's submodule system, which allows developers to get copies of ("clone") and update copies of multiple related repositories at the same time; as developer Chad Horohoe explained, the primary-use case is to allow developers to replicate their pre-switchover ability to grab the code from all WMF-hosted extensions simultaneously. The update has not prevented work on a competitor review system: named "Gareth" and developed by long-time volunteer developer Daniel Friesen, the code review system is an attempt to provide a more homegrown, MediaWiki-compatible review experience (also wikitech-l).
Two billion mobile pageviews: Mobile devices accounted for some 2.089 billion pageviews in April 2012, as reported on Thursday via the Wikimedia blog. The monthly figure, the first to break the self-set two billion pageview target, represents a 187% year-on-year increase, WMF Senior Manager Amit Kapoor reported on behalf of the WMF mobile team in his blogpost addressing the milestone – a jump which he attributed to improvements in both the standard mobile site and device-specific "apps" during the last calendar year. The figures for non-English Wikipedias look particularly encouraging: among those wikis seeing enormous jumps in mobile device browsing, the Portuguese Wikipedia clocks in with 600% growth, Arabic with 500% growth, and Turkish with 800% growth. Several less-developed countries are also set to gain in the second half of this year with the wider rollout of Wikipedia Zero, although the list of countries is protected by commercial confidentiality agreements.
Two performance and two preference problems: Wikimedia wikis suffered two performance issues in the past seven days, one prompting "failed images, scripts, and other static resources" for almost an hour on April 30 (Wikitech incident documentation), the other causing image corruption and various related and unrelated issues for at least four minutes on 3 May 2012 (Wikimedia Commons Village Pump). Two changes to default preferences (enabling email watchlist notifications and edits-add-to-watchlist by default) also went amiss during the week, the result of a problem related to distinguishing between the default preferences of new users preferences and those of older users who had simply never overridden the defaults; consequently, users registered more than a couple of years ago found that their preferences had mysteriously changed overnight until both changes were reverted pending a proper fix for the issue.
A mockup of the "Curation Bar", half of the New Pages Feed (previously called "New Page Triage")
Mixed news for New Pages Feed project: As reported in last week's "Technology report", this week should have seen the deployment of one of the two halves of the New Pages Feed (formerly "New Page Triage") project. Bugs encountered during the first attempted deployment of this new "list view" – essentially a successor to Special:NewPages – forced a second attempt to be scheduled later in the week. That attempt was also unsuccessful, prompting a third attempt to be scheduled for May 7 2012 (PDT). The second half, community liaison Oliver Keyes reported in a newsletter this week, will take the form of a new "toolbar, which we're calling the 'curation bar'; you can see a mockup here. A stripped-down version of this should be ready to deploy fairly soon after the list view is [deployed]". When fully released, the 'curation bar' will contain many options to interact with the page including patrolling it, adding maintenance tags and nominating it for deletion, Keyes says.