Editor retention: Editing tools
In May, the VisualEditor team worked to complete the major new features we have prioritised over the past few months. Our objective is for VisualEditor to be the default editor for all Wikipedia users, capable of letting them edit the majority of content without needing to use the wikitext editor, in July 2013. We have focussed on four areas of new functionality: adding and editing inclusions of references, templates, categories and media items. Our main area of work over the past month has been on references and templates, and we now have implemented editing them in our experimental code; category editing is nearly complete and should be made available very soon. The deployed alpha version of VisualEditor was updated twice (1.22-wmf4
), adding a number of user interface improvements, including further work on the back-end to better support the new features, and fixing a number of bugs.
In May, the Parsoid
team implemented several new features, as well as important performance optimizations in preparation for the July VisualEditor release.
A major image handling overhaul enabled rendering and editing of all image-related parameters with a relatively simple DOM structure
. Template and extension editing was improved to support editing of templates within extensions. This lets editors modify and add templated citations in VisualEditor, an important feature to improve the quality of articles in Wikipedia.
On the performance front, we are now reusing expensive template, extension and image expansions from our own previous output to avoid most API queries after an edit. This is necessary to avoid overloading the API when tracking all edits on Wikimedia projects. A cache infrastructure with appropriate purging was set up and will be tested at full load through June.
At the Amsterdam hackathon, we helped developers leverage our rich HTML+RDFa DOM output
for projects like a Wikipedia-to-SMS service or the Kiwix offline Wikipedia reader
Editor engagement features
In May, we released new features and bug fixes for Notifications on the English Wikipedia and mediawiki.org. Ryan Kaldari, Vibha Bamba and Fabrice Florin collaborated with community members to develop a ‘new message indicator’
, to inform users when someone posts on their talk page. The team also released a new ‘Thanks notification
‘ that lets editors show their appreciation to users who make helpful edits, and offers a quick way to give positive feedback on Wikipedia. Benny Situ developed a feature that marks messages as read when you visit your talk page and expanded our first metrics dashboards
, in collaboration with Dario Taraborelli and Aaron Halfaker. New team member Erik Bernhardson developed several new features, such as updating talk page notifications to link directly to their sections. Luke Welling continued to develop HTML Email notifications
. Fabrice Florin worked with Oliver Keyes to discuss this product with a wide range of community members, and led the team to plan the next steps
for Notifications and other editor engagement features. To learn more, visit the project portal
, read the FAQ page
and join the discussion on the talk page
In May, we developed a few last features and bug fixes on the English
Wikipedias. As requested by community members, Matthias Mullie developed a new opt-in feature that makes it easier to enable or disable feedback on a page
, as well as new UI improvements to simplify the feedback page, based on designs by Pau Giner and specifications by Fabrice Florin. The team also released new feedback links
and tested the auto-archive
feature on prototype. For tips on how to use Article feedback, visit the testing page
, and let us know what you think on this talk page
. Feature development has now ended for this project, and we will determine our next steps based on the upcoming community vote on the German Wikipedia in coming weeks.
Discussion portals were announced
and opened on three wikis: the English Wikipedia
, and mediawiki.org
. An interactive prototype
was released to the public for discussion. Discussion is on-going, and the definition of the “minimum viable product” is being worked on.
Editor engagement experiments
Editor engagement experiments
In May, the Editor Engagement Experiments team (E3) launched its redesigns of account creation and login
forms, after numerous bug fixes and working with local communities to customize the interface as needed. The initial rollout was to 30 of the largest Wikimedia projects in English and other languages, including Wikipedia, Wikimedia Commons, Wikidata, Wikivoyage, Wikispecies, Wikiquote, Wiktionary, Wikibooks, Wikiversity and Wikisource. Complete deployment as the default for all remaining projects was enabled early in June.
Also this month, the team launched and tested a major revamp of the “Getting Started”
interface for onboarding new Wikipedians
(in English). This included a redesigned landing page, a refactor of the backend to increase speed and stability, a new navigation toolbar on articles that new users were given as their first editing task, and a guided tour
to help them complete their first edit. The results of A/B testing
of this new version showed the largest increase in click-through rates for the landing page – up to 32%, a large increase over the 10-12% click-through rate of previous versions. Overall, it also showed a small but statistically significant increase in the rate of first time edits (+1.7%) by new English Wikipedians invited to participate in Getting Started.
Last but not least, the PostEdit extension
(previously enabled on most of the top Wikimedia projects by size) was migrated to MediaWiki core. With this change, the post-edit confirmation message
will be available on all projects, and will be more easily integrated in to VisualEditor
2012 Wikimedia fundraiser
The Operations team moved db1025 into the firewalled fundraising cluster (frack), rebuilt it on Precise with MariaDB. RAID monitoring tools were updated to support RAID controllers used in frack. We’ve mostly finished building/puppetizing the new payments listener (thulium) as well as a new CiviCRM host (barium), both of which are in frack.
The last round of major bugs have been fixed in the Universal Language Selector (ULS) before we start phased its deployment over the month of June across hundreds of Wikimedia websites. Communications announcements have been started for the first phase of deployment which includes removal of Narayam and WebFonts from sites before ULS is rolled out with the same integrated feature set. Test scenarios for ULS have been identified in detail. Implementation of automated tests is in progress. A combination of ULS integration and cross browser testing is in progress. Final performance tweaks are in progress before we get ready to launch the redesigned home page of Translatewiki.net in June. The monthly version of the Mediawiki Language Extension Bundle (MLEB) was released on May 29.
jQuery.webfonts and jQuery.IME continue to be in maintenance mode with new input methods added to our repository this month. jQuery.ULS is being actively updated to reflect design changes suggested by the Product team as well as bug fixes.
Language Engineering Communications and Outreach
The Language Mavens met and discussed areas they can contribute to for Language tools. As part of GSoC 2013, all developers on the team are set to mentor 4 Language Engineering projects supporting jQuery.IME, Language Coverage Matrix, RTL support for Visual Editor and Translate mobile app. Monthly office hours and bug triage were held. The team continued to report and blog on its activities. Hackathon organization and participation at Amsterdam and Tel Aviv were very successful.
This month, the team launched Wikipedia Zero with Mobilink in Pakistan, refactored legacy codebase, migrated configuration from monolithic wiki articles to per-carrier JSON configuration blobs, generated utility scripts, patched legacy hyperlink redirect and content rendering bugs, and supported partner on-boarding.
Mobile Web Photo Upload
This month, we’ve pushed the ‘Nearby’ view to the stable version of the mobile site. Now, with a location-aware device, you can easily identify articles close to your current location. We’ve also made ongoing improvements to photo uploads and the photo upload experience, including improved messaging around image quality and copyright requirements for new uploaders in the beta version of the mobile site. The upload features in general have been a great success, as we’ve sustained over 1000 unique uploaders
over the last two months. We are continuing to experiment in the beta version of the site with improvements to article editing, an improved reorganization of site navigation, Echo notifications, talk pages, and simplifying discovery of article actions (eg editing and watching). We plan to launch these beta features over the course of the next month.
was released, followed by a MediaWiki 1.21.1 maintenance release.
After deploying Score
in April, various performance improvements and fixes were merged in May. To improve scaling of large images, the VipsScaler extension
was prepared on the cluster and is ready for deployment in the next weeks. TimedMediaHandler
had various bug fixes and the libraries used to encode WebM videos were updated to improve quality and address encoding issues.
Wikidata continued to roll out updates to the client (what lives on the various project wikis) and repository (what powers wikidata.org) software; see the wikidata newsletter for more information: May 3rd
and May 24th
. Additionally, there was Operations-related work to create helpful URL redirects for entity matching along with fixes to the logging of autopatrolled edits (which was causing massive database usage and issues when doing archival dumps). These URL redirects and autopatrol fixes should go out in June.
Site performance and architecture
Many MediaWiki developers met in Amsterdam
to discuss architectural principles
and the RFC process.
Admin tools development
This month the team worked on Single User Login finalisation
, which will mean that all user accounts will be global across all of Wikimedia’s public wikis, and so allowing for cross-wiki notifications and better tools for editors. This will require all user accounts to be uniquely named and not conflict with other accounts. Some more work was done on the global account renaming tool
. The team attended the Wikimedia Hackathon 2013 in Amsterdam
where we discussed issues with admin tools and plans for the future with a number of volunteer developers.
Security auditing and response
We released MediaWiki 1.20.6/1.19.7 and provided security training for developers at the Amsterdam Hackathon.
Several engineers at the Wikimedia Foundation met with Facebook engineers to discuss potential deployment of HHVM in 2013 (summary
). We formed the HipHop mailing list
to discuss moving forward with this work.
In May, QA worked with a number of parties both in and outside the Wikimedia Foundation to test Echo, VisualEditor, Universal Language Selector, and other projects. We began an official QA mailing list
In May, Ariel Glenn helped out setting up missing bits of infrastructure to the beta cluster. He added a Redis instance (that holds the job information) and HTTPS support
. HTTPS will let us write scenarios related to logging in on the wiki or via a mobile device; it will also let us test out OAuth.
udp2log archiving is now working reliably. Max Semenik has set up an EventLogging infrastructure on beta, and Niklas Laxström enabled Universal Language Selector. The Job processing was malfunctioning but was restored.
Since April 30, the MediaWiki instances are using NFS, which is much faster than the previous GlusterFS share; pages serving time went from 560 ms to 260 ms.
Roan Kattouw has deployed Parsoid and VisualEditor on beta. Just like in production, users can enable it in your their preferences under ‘Editing’.
In the beginning of May, Jenkins/Zuul faced overload for a few days; this was resolved by upgrading Zuul and tweaking some time-expensive part of the code. Zuul now lets us define which jobs it triggers by using a predefined template which makes it easier to add new projects. Zuul is now faster to report changes back to Gerrit, which was a complaint during rush hours.
The Wikibase client and repo components are now tested in Jenkins. All puppet repositories are now verifying the puppet manifests and erb templates for syntax validity. The Qunit tests being run for MediaWiki core and VisualEditor seem to be in good shape.
PHP CodeSniffer has been upgraded as well as the standard for MediaWiki code. We have yet to enforce it though, since the current code base does not pass the standard.
In May, we added beta labs as a target for automated browser tests, which allowed us to create tests for the Universal Language Selector at the Hackathon in Amsterdam. We shored up a lot of Jenkins builds at the hackathon as well. We created our first test for VisualEditor, and we are looking forward to working with Rachel Thomas (as part of the Outreach Program for Women) to create more.
We continued our efforts of increasing our monitor coverage of the different webrequest dataflows. On the udp2log side, we added monitoring per DC/server role
. Every month, we work on improving the robustness and security of the analytics-related servers that we run: we moved the multicast relay from Oxygen to Gadolinium, we upgraded Oxygen to Ubuntu Precise, and we moved all the Limn-based dashboards from the Kripke labs instance to the Limn0 labs instance. Continous integration for webstatscollector, wikistats and udp-filters now works. The puppet module for Hadoop
has been merged in the Operations reposotiry; this is a big step forward in moving Kraken from beta to production status. Magnus Edenhill demonstrated varnishkafka based on Kafka 0.8; on a local machine varniskafka was able to process 140k msgs/s and we are planning to do production testing mid June. Last, we separated the Kraken machines from the other production servers by installing network ACLs.
Analytics Visualization, Reporting & Applications
For the mobile team, we started collecting pageview counts
for both official and non-official Wikipedia apps. We changed our Kafka import configuration so that the raw webrequest folders are directly queryable using Hive. The decision was made to re-platform the UMAPI codebase; we have spent quite some time specifying user stories
and had productive discussions about the architecture during the Amsterdam Hackathon. On the development side, the ‘page count’ metric was introduced. We adapted Ori Livneh’s Mediawiki Vagrant VM to also support UMAPI in combination with test data. This will make it much easier to debug issues and open development up to community members. We also fixed numerous stability bugs.
A Wikimedia Labs instance
to test Bugzilla software changes and a patch to puppetize Bugzilla
are now available (thanks to Ori Livneh
). This will make updating Bugzilla to newer versions and reapplying Wikimedia’s custom patches much easier. A MediaWiki Installer bugday
took place in preparation of the MediaWiki 1.21 release, as well as an IRC office hour
. Andre Klapper worked on a proposal for a Bugzilla admin policy
. In Bugzilla’s configuration, the number of Bugzilla administrators
has been decreased in order to improve coordination. As a side-effect of his investigation, Andre documented
the meaning of Bugzilla admin rights.
We selected 20 Google Summer of Code
and 2 Outreach Program for Women
projects that will be mentored by a total of 32 volunteers. This represents more than double the amount of projects we had last year. We received 69 applications from 60 students for Google Summer of Code 2013, from which 9 were also applying to OPW, and 4 OPW-only individual applications. Google allocated the 21 slots we requested, but we decided to give one back in order to keep a standard on project feasibility.
In May, Guillaume Paumier
‘s major focus was on supporting Tech ambassadors
and setting up Tech news
, an initiative aiming to collaboratively monitor recent software changes likely to impact Wikimedians, and distribute a weekly summary, free of technical jargon, to subscribers on their talk page. Two issues of this weekly summary were published this month; starting with the second issue, the content is now distributed in several languages if translations are available. Guillaume also continued to review technical blog posts, and executed the move of the Mobile documentation
from Meta-Wiki to mediawiki.org.
Volunteer coordination and outreach
has been preparing a proposal to get automated community metrics
based on vizGrimoire
and provided by their maintainers, Bitergia
. It is currently being discussed with Sumana Harihareswara
and Rob Lanphier
for budget approval. Quim also worked on a user-friendly template for the landing page of the wikitech-announce
mailing list that can be used for other Wikimedia lists (source code
). He also created a landing page for organizations
willing to collaborate with Wikimedia to co-organize technical activities.
Can you help us translate this article?
In order for this article to reach as many people as possible we would like your help. Can you translate this article to get the message out?