Wikimedia Engineering

Language:	English  • Deutsch

Tech Forum

Tech News

Tech Ambassadors

Wikimedia Engineering

MediaWiki

The Wikimedia engineering team builds, improves and maintains the technical infrastructure of Wikimedia sites (software and hardware), by supporting and complementing volunteer efforts. It's composed, among others, by engineering and product development staff employed by the Wikimedia Foundation and by other organizations in the Wikimedia movement.

• Platform
• Features
• Mobile
• Language
• Analytics

Latest report Major news in November include: the release of the second version of the Content Translation tool, which heavily relies on Apertium for machine translation; updates to MediaWiki's internationalization based on new CLDR data; the move from Bugzilla to Phabricator as the new collaboration platform for the Wikimedia technical community. Read more Featured activity Wikipedia Zero Free and zero rated access to Wikipedia through our partners Status: (2014-11-monthly) During November 2014, the Partners engineering team continued work on the the partners portal (ZeroPortal) minimum viable product ("MVP"), further improved the fidelity of zero-rated Graph extension pageview statistics relative to the legacy Limn graphs and identified further page filtering criteria, generated statistics on basic pageviews by JavaScript support level in both Wikipedia Zero and general mobile web Wikipedia, added basic scheduled runs of the portal Cucumber tests, added colorized indicator support to the Wikipedia for iOS Wikipedia Zero experience, fixed the broken "x" close button on Wikipedia Zero banners, and finalized the speedier mdot landing page and language-aware redirect code for Wikipedia Zero users. The team also consulted with partners on API usage and zero-rating implementations. Team: Dan Foy (Tech Manager), Yuri Astrakahn, Adam Baso, Jeff Hobson Latest news Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available. Recent software changes You can now use {{#lsth: PageName | SectionName }} to transclude a section with its title. [1] Problems MediaWiki was reverted to the previous version on February 4. It was because of a performance issue. It was restored later. [2] UploadWizard was broken on February 4 because of the revert of MediaWiki. [3] All sites were broken for 30 minutes on February 5. It was due to a network problem. [4] Software changes this week The new version of MediaWiki has been on test wikis and MediaWiki.org since February 5. It will be on non-Wikipedia wikis from February 10. It will be on all Wikipedias from February 11 (calendar). You can have one user page for all wikis. Your Meta user page will show if you don't have a user page on a wiki. You can test this tool on test wikis. [5] [6] [7] You can search for media files in VisualEditor more easily. Images are bigger and you see the size and license. [8] [9] It is easier to review your changes when you save the page in VisualEditor. The window is wider. [10] You can read the latest news about VisualEditor. You can now join weekly meetings with developers. During the meetings you can tell developers which bugs are the most important. The first meeting is on February 11 at 20:00 (UTC). Future changes Administrators will soon be able to delete change tags used fewer than 5,000 times. [11] In the future you will be able to have personal lists of articles on the mobile site. [12] Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

See the status dashboard Stay informed Wikimedia Technology Blog — And its corresponding feed. Calendar — All events. wikitech-announce — Subscribe to announcements of new activities. Get involved How to contribute Tell us if you run into a problem Become a MediaWiki developer Test our mobile site, or build mobile apps Chat with us Figure out ways to encourage new Wikimedia editors Help to update the engineering project documentation Job openings Are you looking to work for Wikimedia? We're hiring! Director of Engineering Senior Software Engineer - Services Software Engineer - Flow (Front-end) Software Engineer - Mobile - Android Application Security Engineer Full Stack Developer - Analytics Agile Coach Scrum Master Senior Technical Product Manager Community Liaison Community Liaison (PT Contract) UX Senior Designer UX Senior Design Researcher UX Visual Design Fellowship Tools New to project pages? Have a question about how things work? Read the how-to guide. See also Dynamic list of all projects (including those completed) Trello boards Mingle projects, including Wikimedia Language engineering and Analytics

Features engineering VisualEditor — Creating a visual editor for MediaWiki, other platforms and the Web at large Editing — Extending and improving the editing tools used at Wikimedia Parsoid — A bidirectional runtime wikitext parser. Converts back and forth between wikitext and HTML/XML DOM with RDFa. Services and REST API — Team implementing backend services and a REST-style content API as a step towards a service-oriented architecture. Flow — User-to-user communication and collaboration. Fundraising tech — Technical work supporting the Wikimedia Foundation's fundraising efforts Growth — To create sustainable growth in the community of editors on Wikimedia projects. Mobile engineering Wikimedia Apps — Wikimedia Mobile Applications for iOS, Android, and new platforms Wikipedia Zero — Free and zero rated access to Wikipedia through our partners Mobile web projects — Features and design work on the Wikimedia MobileFrontend mobile gateway Platform engineering HHVM — Support in MediaWiki for HHVM (HipHop Virtual Machine) and deployment to the Wikimedia cluster Admin tools development — Feature development and bugfixes on tools for stewards and local power-users Search — Search infrastructure maintenance and overhaul Wikidata deployment — Regular deployments to wikidata and clients SUL finalisation — Resolve any remaining clashing user names, so that in the future every user may have a single username to log in with on all Wikimedia projects. Library infrastructure for MediaWiki — Enable management of MediaWiki codebase using versioned dependencies Editing performance — Improving the user-perceived performance associated with all aspects of the editing experience Wikibase indexing — Get a WDQ-like thing into production! Shell requests — Ongoing processing of Phabricator requests that require shell access to fix Security auditing and response — Inspection of code and training of developers Quality Assurance — Software testing and quality assurance for Wikimedia engineering activities Browser testing — Automated testing of MediaWiki within various browsers to improve quality Multimedia — Handling of images, sound and video files, from infrastructure to contributions, curation, publishing and viewing. Bug management — Management of Wikimedia's bug tracker. Phabricator migration — Preparation and execution of the migration of our development toolchain to Phabricator Outreach programs — Google Summer of Code, LevelUp, Outreach Program for Women and other programs that mentor contributors Events coordination — Organization of physical and online events Documentation improvement — Improve MediaWiki docs (bug 1) Language engineering Language tools — Internationalization and Localization tools to enable use of Wikimedia projects in various languages. Milkshake — Create generic i18n tools in jQuery Language Engineering Communications and Outreach — News about Language Engineering activities and Outreach programs Content translation — Content translation of Wikipedia pages Analytics Wikimetrics — Cohort analysis of Wikimedia editors Data Processing — Pipe volumes of data into Hadoop for research and reports Editor Engagement Vital Signs — Dashboard to expose Editor Engagement and the impact of product decisions. EventLogging — Sensibly capture Mediawiki usage data to help improve products. Research and Data — Supporting the Wikimedia Foundation in using data to make better decisions Operations The Operations team is responsible for the technical infrastructure of Wikimedia sites: this includes the data centers, servers and network. They document most of their work on the wikitech wiki.