- 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 — Initial ideas for the user "home page" feed system, including modules.
- Wikipedia Education Program — A MediaWiki extension to support the Wikipedia Education Program
- Fundraising tech — Technical work supporting the Wikimedia Foundation's fundraising efforts
- Growth — To create sustainable growth in the community of editors on Wikimedia projects.
- Site performance and architecture — Various initiatives geared toward improving site responsiveness, decreasing resource consumption, and/or improving site maintainability
- 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
- Auth systems — Improvement of authentication and authorization systems, and adding new auth mechanisms such as OpenID and OAuth
- Deployment tooling — Improve the deployment process and operational monitoring capabilities in use for the Wikimedia content projects and related infrastructure.
- 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
- Shell requests — Ongoing processing of Bugzilla requests that require shell access to fix
- Security auditing and response — Inspection of code and training of developers
- Release Engineering — Working to improve the quality of code and reduce the time it takes users to get it.
- Quality Assurance — Software testing and quality assurance for Wikimedia engineering activities
- Beta cluster — Establish a functional, production-like environment in Wikimedia Labs suitable for final-stage testing of new features.
- Continuous integration — A testing platform to provide continuous quality control for MediaWiki
- 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.
- UploadWizard — A feature that provides an easier way of uploading files to Wikimedia Commons, the media library associated with Wikipedia.
- Structured Data — Improve how to store and retrieve metadata on Wikimedia Commons, the media library associated with Wikipedia.
- Bug management — Management of Wikimedia's bug tracker.
- Phabricator migration — Preparation and execution of the migration of our development toolchain to Phabricator
- Mentorship programs — Google Summer of Code, LevelUp, Outreach Program for Women, and other programs that mentor contributors
- Volunteer coordination and outreach — Coordination of volunteer efforts, technical outreach and recruitment of new volunteers
- Architecture process —
- dev.wikimedia.org — A central place for 3rd-party developers to access our data sets and experiment with our APIs
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.
|