Good first bugs

This page provides a list of little bugs and tiny missing features which annoy users and which are relatively easy for a new MediaWiki coder to fix. These are a good way to start getting familiar with the MediaWiki code base. You must have read the "Get started" section of How to become a MediaWiki hacker already to understand the infrastructure, workflows and communication expectations.

Potential bugs to work on
The following sections describe a few example areas in which you can contribute, but you are not limited to these areas!

In the upper right corner of a bug report you can see the product and component that the problem is located in. This provides you a hint about the Git repository that the code is located in, and about the development team which you could contact if you want to discuss it in a "broader" way (as comments in bug reports should preferably refer to the specific problem described in the report only).

MediaWiki
MediaWiki is the core software which provides basic wiki functionality. It is written in PHP. Ask your general development questions on the wikitech mailing list and the #mediawiki-dev and #mediawiki IRC channels.


 * Open easy MediaWiki bug reports and enhancement requests

Pywikibot
PyWikibot is a Python-based framework to write bots for MediaWiki. Ask your general development questions on the Pywikibot mailing list and the #pywikibot IRC channel.


 * Open easy Pywikibot bug reports and enhancement requests

Language Engineering (Localization/Translation/Internationalization)
Ask your general Language Engineering development questions on the mediawiki-i18n mailing list and the #mediawiki-i18n IRC channel.


 * Open easy Language Engineering bug reports and enhancement requests

Multimedia
Ask your general Multimedia development questions on the multimedia mailing list and the #wikimedia-multimedia IRC channel.


 * Open easy Multimedia bug reports and enhancement requests

VisualEditor and Parsoid
VisualEditor is MediaWiki's WYSIWYG editor. Ask your general VisualEditor development questions on the wikitech mailing list and the #mediawiki-visualeditor IRC channel.


 * Open easy VisualEditor bug reports and enhancement requests

VisualEditor is powered by Parsoid, a wikitext parser and runtime. Ask your general Parsoid development questions on the wikitext mailing list and the #mediawiki-parsoid IRC channel.


 * Open easy Parsoid bug reports and enhancement requests

Mobile Apps
There are numerous applications for mobile devices (Android, iOS, Windows Phone, …) to access Wikimedia wikis. Ask your general development questions on the Mobile mailing list and the #wikimedia-mobile IRC channel.


 * Open easy Mobile applications bug reports and enhancement requests

Wikidata
Wikidata is a centralized knowledge base for structured data, such as interwiki references and statistical information. Ask your general development questions on the Wikidata mailing list, the #wikidata IRC channel and on the wiki.


 * Open easy Wikidata bug reports and enhancement requests

Analytics
The Analytics team empowers and supports data-informed decision making in Wikimedia. Ask your general development questions on the Analytics mailing list.


 * Open easy Analytics bug reports and enhancement requests

Design
Fixing design bugs or requests requires existing graphics skills working with a Vector graphics application (e.g. Inkscape). Basic knowledge of CSS can also be helpful for integration. Ask your general development questions on the Design mailing list and the #wikimedia-design IRC channel.


 * Open easy design bug reports and enhancement requests

System messages and localization/translation problems
System messages in MediaWiki or its extensions often need small corrections to the English text, but the source text can only be changed in the code by developers, contrary to translations. This has grown into a large backlog of usually very easy fixes (which might be as easy as fixing a typo).

Also, many messages are unclear and require better documentation (see Localisation). Missing documentation can also be added by just editing the  subpage of the message on translatewiki.net, like all translations, but may require some study of the code to understand what a message is for: it's therefore optimal to start understanding the code, and very useful for the translators (who do not have such skills).


 * Open string change bug reports and enhancement requests (under "Blocked by")

Documentation

 * Open bug reports and enhancement requests related to documentation with the "easy" keyword

And many more…
Still not enough ideas? There are more fields you can explore - MediaWiki has hundreds of extensions and tools! Check out the complete list of bugs recommended for new contributors:
 * open bug reports and enhancement requests with the "easy" keyword

If you have any trouble or questions, please feel free to contact Quim Gil or Andre Klapper or ask for help via IRC.