Developers/Maintainers

This page lists developers who know the most about, and help maintain, core MediaWiki components, key extensions and skins, libraries and other Wikimedia technical infrastructure.

Terminology

 * Developers contribute to the code of MediaWiki software. They commit changes to the central Git repository by pushing changes for review in Gerrit where the latest copy of the software is stored. Developers include paid Wikimedia Foundation staff and volunteers. For more details, see Developers. Anyone can create a developer account and submit patches to Gerrit for review. Anyone may participate in Phabricator and in Gerrit to help investigate or review code and gain experience that way. If you're seeking to become an active maintainer, feel free to contact a steward or maintainer and share this desire by asking if they're willing and able to mentor you proactively for a certain period of time.
 * Maintainers have +2 access to the relevant Git repository and they regularly respond to bug reports and changeset review requests. Only maintainers can merge changes in Gerrit. Anyone may participate in Phabricator and in Gerrit to help investigate bugs or review code and gaining experience that way. If you're seeking to become an active maintainer, feel free to contact a steward or maintainer and share this desire by asking if they're willing and able to mentor and involve you proactively for a certain period of time.
 * Stewards are teams at organizations with professional responsibility over the development and overall health of the component. They commit to a base level of support such as high priority bug fixes and code reviews. A stewarding team must one or more developers that can act as Maintainer, which means they can write changes but also have +2 access to the relevant Git repository to merge changes. In most cases, a steward is also the primary (and only) maintainer. For more information regarding stewardship, see Development policy/Code Stewardship.


 * Individual maintainers are developers that act as primary maintainer in lie of a steward. This is usually the case for components that have no assigned steward (e.g. components that are volunteer-led), or where the steward has agreed to be a fallback.
 * Consultants are developers that have signalled an intent to answer questions or assist with problems, but should not be confused with maintainers. These may be former maintainers, or contributors in training,.

MediaWiki core

 * See also: Gerrit's list of mediawiki group members (core developers with +2 on all mediawiki repositories).

MediaWiki extensions deployed at Wikimedia Foundation

 * See also: Category:Extensions used on Wikimedia and source/mediawiki-config/browse/master/wmf-config/extension-list

MediaWiki skins deployed at Wikimedia Foundation

 * See also: Category:Skins used on Wikimedia and source/mediawiki-config/browse/master/wmf-config/extension-list

Libraries deployed with MediaWiki at Wikimedia Foundation
For upstream libraries that we bundle, see Upstream projects. For other libraries that we publish see doc.wikimedia.org (includes developer dependencies, and projects not used by MediaWiki).

MediaWiki core libraries
See also the composer.json and foreign-resources.yaml files in MediaWiki core.

Frontend and backend libraries that are published by Wikimedia and bundled with MediaWiki core.

Upstream projects and libraries
There are many upstream projects on which MediaWiki, extensions, and/or Wikimedia depend. Some of them were "invented here", as stand-along libraries, or split out as part of the Library infrastructure for MediaWiki project. Some of them are widely-used third party tools to which community members provide improvements or support. Others are merely used with gratitude.

Services and administration

 * See also: wikitech:Category:Services and FLOSS-Exchange

If you need immediate help with a systems administration question, please go into the IRC channel and find the person currently on Ops Clinic duty" (as listed in the  ).

Other areas of focus
(Not all of them fit in current projects.)


 * User experience, user interface and visual design: the Wikimedia Design group members and others
 * Site performance (speed and consistency of responses): Wikimedia Performance Team
 * Multilingual aspects: Nikerabbit and others.