Developers/Maintainers

This is a list of developers who know the most about, and maintain, MediaWiki core, key extensions, and Wikimedia servers. To be listed as a maintainer a person has to have +2 access to the relevant Git repository and regularly respond to bug reports and changeset review requests.

If you are a maintainer, please consider using configuring Gerrit to send you an email for new patchsets in a repository. Alternatively you can add yourself to the Gerrit Reviewer Bot which will automatically add you as a review to each new patchset.

Anyone can list themselves as in training to maintain something, signaling that they want to learn more and achieve maintainership within the next year.

MediaWiki core

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




 * }

MediaWiki extensions deployed by WMF

 * See also: Category:Extensions used on Wikimedia and Extension Matrix/stable




 * }

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.

Key extensions
Mostly extensions used by over ~400 standalone wikis.




 * }

Operations/systems administration

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

If you need immediate help with a systems administration question, please go into #wikimedia-operations and find the person currently "on RT/interrupts duty" (as listed in the ).




 * }

Analytics

 * See also: Analytics team homepage, WMF Analytics on GitHub




 * }

Other areas of focus
(Not all of them fit in current components, see also Bugzilla taxonomy.)


 * HTML forms (for a unified visual design and form features): not sure
 * User interaction: the Design group and others
 * Visual design: the Design group team and others
 * Site performance (speed and consistency of responses):, Ori Livneh, and Aaron Schulz (see also Site performance and architecture)