Annoying little 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.
- 1 Potential bugs to work on
- 1.1 MediaWiki
- 1.2 Pywikibot
- 1.3 Language Engineering (Localization/Translation/Internationalization)
- 1.4 Multimedia
- 1.5 VisualEditor and Parsoid
- 1.6 Mobile Apps
- 1.7 Wikidata
- 1.8 Discovery / Search
- 1.9 Analytics
- 1.10 Design
- 1.11 Skins
- 1.12 System messages and localization/translation problems
- 1.13 Documentation
- 1.14 Browser Tests & Quality Assurance
- 1.15 Huggle
- 1.16 And many more…
- 2 See also
Potential bugs to work on[edit | edit source]
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[edit | edit source]
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.
Pywikibot[edit | edit source]
Language Engineering (Localization/Translation/Internationalization)[edit | edit source]
Multimedia[edit | edit source]
VisualEditor and Parsoid[edit | edit source]
Mobile Apps[edit | edit source]
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.
Wikidata[edit | edit source]
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.
Discovery / Search[edit | edit source]
The Discovery team builds the path of anonymous discovery to a trusted and relevant source of knowledge. Ask your general development questions on the Wikimedia-search mailing list and on the #wikimedia-discovery IRC channel.
Analytics[edit | edit source]
Design[edit | edit source]
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.
Skins[edit | edit source]
Skins allow users to customize the look and feel of MediaWiki. Basic knowledge of CSS and PHP is helpful. Check the project page in Phabricator for more information on each skin and contact information.
System messages and localization/translation problems[edit | edit source]
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#Message documentation). Missing documentation can also be added by just editing the
/qqq 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[edit | edit source]
Browser Tests & Quality Assurance[edit | edit source]
Automated browser tests help Wikimedia engineers produce quality user facing software faster. See the page on Browser testing for more on what technologies we use and how to get involved. For more general information, see Quality Assurance.
Huggle[edit | edit source]
Huggle is an application for dealing with vandalism on Wikimedia projects, written in C++.
And many more…[edit | edit source]
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:
See also[edit | edit source]
- How to become a MediaWiki hacker
- How to contribute — Learn about more ways how you can contribute to MediaWiki and the free culture community (e.g. translation, documentation, …)
- Possible projects for volunteers willing to dive into more complex challenges
- Triage tasks in Phabricator — if you want to get an idea of issues in the software and help developers to save some time
- Oldest open changesets in Gerrit — your help reviewing them is welcome