Editor retention: Editing tools
VisualEditor
In August, the VisualEditor team continued work, and presented and ran workshops at
Wikimania in Hong Kong to discuss how to best improve the system. The deployed version of the code was updated three times (
1.22-wmf13,
1.22-wmf14 and
1.22-wmf15), with several mid-deployment releases as the code was developed to patch urgent issues. The focus in this work was in improving the stability and performance of the system, fixing a number of bugs uncovered by the community, and making some usability improvements.
Parsoid
In August, the Parsoid team continued to polish compatibility with existing wikitext. User feedback after the July VisualEditor release was instrumental in the identification of issues and the development of support for important use cases of creative templating.
The increased team size also allowed us to perform some long-standing code cleanup, make Parsoid compatible with Node 0.10, and improve testing. The
round-trip testing infrastructure received a much-needed overhaul. The storage back-end switched from SQLite to MySQL, which improved throughput a lot and is allowing us to test new code far more quickly than before. Performance statistics are now recorded, which will let us identify performance bottlenecks as well as catch performance regressions.
During Wikimania, the Kiwix team used Parsoid output to create an offline copy of Wikivoyage. With standard HTML libraries and the rich RDFa information in the Parsoid DOM, downloading and modifying the HTML representation was done in about
1000 lines of JavaScript.
Editor engagement features
Notifications
In August, we released Notifications on the French, Hungarian, Polish, Portuguese and Swedish Wikipedias, after extensive testing on the English Wikipedia, as well as mediawiki.org and Meta-Wiki. This engagement tool was well received by our new communities, especially social features such as Mentions and Thanks, which enable users to communicate more effectively than before. Benny Situ led the engineering work for this deployment and fixed a number of bugs, with the help of Erik Benhardson and Matthias Mullie. Fabrice Florin managed community relations for these new releases, updating this
release plan and reaching out to more projects, to prepare for worldwide deployments on all wiki projects in coming months. To that end, we teamed up with Philippe Beaudette, Maggie Dennis, Patrick Earley, Jan Eissfeld, Anna Koval, Keegan Peterzell, and Sherry Snyder to coordinate these releases with the communities they serve. Dario Taraborelli created new metrics dashboards
for French,
Hungarian,
Polish,
Portuguese and
Swedish Wikipedias. Lastly, we presented our work on Notifications in two talks at Wikimania 2013, with both
a general overview and
a technical presentation (
see slides). We are very grateful to all our community champions for each language and look forward to more collaborations in the future. Our next major deployment to non-English Wikipedias will take place on Sep. 17, to be followed by weekly releases throughout the fall, as outlined in our
release plan. To learn more, visit the
project portal, read the
help page and join the discussion on the
talk page.
Flow
In August, we continued development of the Flow prototype by implementing revisioning,
moderation, and display code, on top of the storage and block abstractions. We have deployed this prototype to an internal labs instance to encourage the full team’s involvement in development. Additionally, we participated in an
agile workshop run by Arthur and Tomasz from the mobile team. This workshop facilitated planning the Flow MVP and setting goals for the team’s first development sprint, along with providing information about agile guidelines and practices that have worked well for the mobile team.
Article feedback
In August, we made a few feature tweaks and bug fixes for the
Article Feedback Tool (AFT5) on the
English and
French Wikipedias. Matthias Mullie released a few patches to improve the
opt-in/opt-out tool, and tested the new
feedback notifications to let users know when feedback is marked as useful for a page they watch (or for a comment they posted). We also presented our work on AFT5 at Wikimania 2013, with designer Pau Giner and our French and German champions Benoît Evellin and Denis Barthel, in
this session (
see slides). The team plans to make the AFT5 tool available to other wiki projects interested in testing this tool later this year, as outlined
in the release plan.
Editor engagement experiments
Editor engagement experiments
In August, the Editor Engagement Experiments team (E3) primarily focused on development for its next and final A/B test of the
Getting Started task suggestion system, a part of a project aimed at
onboarding new Wikipedians. The team also worked on enhancements and bug fixes for the
GuidedTour extension, such as adding the ability to customize default tour actions and better integration with
VisualEditor. During part of August, the majority of the E3 team was at Wikimania 2013 in Hong Kong, and delivered three talks, including on:
guided tours, the team’s
new editor onboarding process, and
product management at the Wikimedia Foundation.
Commons App
This month, the Mobile Apps team pushed out additional releases of the Commons photo uploader app for iOS and Android. The iOS version includes a major UI revamp by Monte, while the Android version has received multiple incremental updates by Yuvi and Brion. Yuvi has been working on modernizing support for campaigns in UploadWizard, which will make it easier to coordinate uploads for events like Wiki Loves Monuments. Viewer, contributor, and admin user interfaces for campaigns will come to the web, with campaign-tied uploading in the web and mobile app. The team also started making plans for the next generation of the Wikipedia reader app, which will be more closely integrated with the mobile web site to ensure that new features are always available through a web view, even where we don’t create specific native support. More details will be put together in the next couple months.
Wikipedia Zero
This month, the team completed version 1 of Wikipedia Zero automation tests, continued programming the re-architecture of Wikipedia Zero, implemented search engine non-indexing, and analyzed HTTPS requirements in support of a push for greater usage of HTTPS across Wikimedia projects. The Wikipedia Zero engineering team thanks Amit Kapoor from the Wikipedia Zero partnerships team, who wrapped up work with Wikimedia Foundation this month, for his hard word getting the program off the ground. And the team is also pleased to welcome Carolynne Schloeder, who joins the Wikipedia Zero program as Director of Mobile, Programs.
Mobile web projects
This month we continued to improve the mobile editing feature, monitoring and triaging bugs and expanding the feature show at the section level of articles. We also released the first iteration of mobile notifications to projects where Echo is enabled (English, French, Polish, Portuguese, Hungarian, and Swedish Wikipedia, as well as and Meta). In beta, we built a new notifications treatment to be released in later months and continued working on mobile talk pages.
MediaWiki Core
Multimedia
In August, we continued to expand our
multimedia team: Bryan Davis joined us as senior platform engineer, working with product manager Fabrice Florin, front-end engineer Mark Holmquist and engineering director Rob Lanphier. We discussed multimedia plans and new feature ideas with community members in two separate events:
a multimedia roundtable at Wikimania 2013 and
an IRC chat, and updated our
multimedia plan for the coming year based on their feedback (
see slides). Summer contractor Brian Wolff completed the development of new gallery tags to support more appealing layouts for thumbnails, while Jan Gerber made improvements to the Score and TimeMediaHandler extensions. Mark Holmquist started development on the
Media Viewer, based on designs by May Tee-Galloway and Jared Zimmerman; this new tool will display images in larger size when clicking on article thumbnails, as well as display file information and a full-screen viewing option, right on the same page. We aim to test a first version of this tool as part of a
beta experiment on a few pilot sites in coming weeks. To discuss these features and keep up with our work, we invite you to join this new
multimedia mailing list. Last but not least, we are also recruiting for two more positions for our team: a
multimedia systems engineer and a
senior software engineer. Please spread the word about this unique opportunity to create a richer multimedia experience for Wikipedia and MediaWiki sites!
Search
In August we deployed CirrusSearch to test2.wikipedia.org and mediawiki.org and we’re testing there. We’re actively looking for other volunteers to test out CirrusSearch. Right now, CirrusSearch is not the primary search for mediawiki.org; you have to use a URL parameter to test it. We’re hoping to make it the primary in September.
Auth systems
The team deployed OAuth to mediawiki.org on Aug 20th, and are working on enhancement requests before the extension is enabled on the rest of the WMF wikis. Several small bugs were fixed in SUL.
Security auditing and response
The team responded to reported issues, and prepared for the next MediaWiki release, scheduled on September 3. We worked with Operations to enable HTTPS for user logins in most geographies.
Quality assurance
Quality Assurance
This month QA began collaborating closely with Release Engineering to coordinate improvement of reporting, monitoring, and testing software releases. Our goal is to make our frequent software releases even more reliable than they already are, and to use the tools and systems in place today such as the beta labs cluster to make those reliable releases even more frequent.
Browser testing
This month saw a significant change to the structure and organization of browser tests, with tests and builds for CirrusSearch, UniversalLanguageSelector, and VisualEditor following the example of MobileFrontend and now residing in the git repositories for those extensions, rather than in the /qa/browsertests repository. This creates opportunities for more frequent and more accurate Jenkins builds of the tests, while also reducing the overhead required for analyzing test failures.
Bug management
Andre gave presentations on
Improving MediaWiki quality: How everybody can help with bug report triaging and
Transparency and collaboration in Wikimedia engineering at
Wikimania 2013. He updated
Bugzilla’s technical documentation and documented
how to test Bugzilla code changes on the Wikimedia Labs instance. Bugzilla
now consequently links to canonical places explaining how to write a good bug report and explaining Bugzilla’s UI fields. Bugzilla also
shows a new “Show other bugs” link next to the “Component” area to make finding similar reports easier. Andre cleaned up his
Greasemonkey triage helper scripts by providing a setting for each functionality at the beginning of the file; a
blog post provides more details.
Bugzilla’s testing instance on Wikimedia Labs saw several patches deployed for testing, which after some more testing should end up in the live Bugzilla; changes include:
showing the history of a bug report inline between the comments and configuring
the guided bug entry form for users that are new to bug reporting.
Mentorship programs
The 20
Google Summer of Code projects passed the official mid-term evaluation at the beginning of August, and the
Outreach Program for Women project is on track as well.
Katie Filbert (Aude),
David Cuenca (Micru) and
Quim Gil (Qgil) will participate at GSoC Mentors Summit in Mountain View (CA, USA) on October 19-20.
Monthly reports from the projects:
Technical communications
Guillaume Paumier continued to focus on the VisualEditor deployment effort, working on communications, documentation and liaising with the French Wikipedia. Work on technical communications mostly focused on perennial activities like
Tech news and ongoing communications support to the engineering staff.
Volunteer coordination and outreach
We had a team presentation at Wikimania:
Transparency and collaboration in Wikimedia engineering, explaining how volunteers can make a difference. Following the work on
Community metrics, the
five key performance indicators (KPIs) were discussed and agreed upon. We are focusing on the first one:
who contributes code. A list of
Key Wikimedia software projects has been created to define the scope of these KPIs. Recruiting automated browser testers keeps being our top priority. We are organizing the next workshop in San Francisco and online on September 18:
Epic fail: figuring out Selenium test results.
Analytics infrastructure
We continue to pursue the initiatives listed in our planning document. We’ve had one analyst accept a job offer (welcome
Aaron!) and are in discussions with a software engineer. We continue to have a solid pipeline and are spending a lot of time interviewing. Wikimetrics is on target for an early September release and we’ve made good progress against our hadoop infrastructure goals. In co-operation with Ops, we’ve completed our reinstall of the Hadoop cluster and run several days of reliability testing over the labor day weekend. We are currently investigating replacing the Oracle JDK with the Open JDK to be in line with our goals of using open source whenever possible. Our project to replace udp2log with Kafka is making steadily progress. Varnishkafka, which will replace varnishncsa, has been
debianized and the first performance tests of compressing the message sets are very encouraging. We created a test environment in Labs to test Kafka failover modes and we have been prototyping with
Camus to consume the data from a broker and write it to HDFS. We are right now thinking about how to set up Kafka in a multi data-center environment. The Zookeepers have been reinstalled through Puppet as well.
Analytics Visualization, Reporting & Applications
In close collaboration with Dario, Jaime and Jessie, we have worked on new features for Wikimetrics. In particular, we are adding new metrics such as survival,
pages created,
aggregation of metrics,
metadata in the CSV output, a
support page and we have now more than
90% test coverage of the codebase. In preparation for the reinstallation of the Hadoop cluster, we moved all Wikipedia Zero jobs off the cluster. We took this opportunity to add additional monitoring to the creation of Wikipedia Zero dashboards. We have worked with Wikipedia Zero to identify a problem with Geolocation of requests that has created large jumps in total traffic. We spent quite some time creating a more robust process for updating and monitoring gp.wmflabs.org. This dashboard is used by various internal stakeholders and receives its information from different datastreams using different scripts. We have been working on running these scripts under the general purpose stats user, adding additional monitoring to prevent stale data and puppetized some of the jobs.
Data Releases
In August, we attended WikiSym and Wikimania.
Dario Taraborelli gave a keynote address on
actionable Wikipedia research at WikiSym, where several other
Wikipedia research papers were presented. At Wikimania, we hosted two sessions focused on
Wikimedia data and
analytics tools. We also worked with Platform engineering this month on analyzing and visualizing
HTTPS failure rates by country, in preparation for the switch to HTTPS as a default. We released new dashboards for the launch of notifications on 5 other Wikipedias and continued to provide ad-hoc support to teams in Editor Engagement. Last, we continued screening and interviewing candidates for an open research analyst position.
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?
Start translation