Good first bugs
This page provides a list of software bugs and small missing features that have been identified as a good way to get involved with an existing Wikimedia project (not only MediaWiki core and its extensions).
This is one way to start getting familiar with the code in Wikimedia projects.
Note that the tasks linked below do not have assigned mentors. You will be mostly "on your own". We recommend to work on software projects with mentors: Check out the list of software projects that we recommend.
No matter which software project you work on, you must have read the Communication tips section to understand workflow and communication expectations.
If you decide to work on MediaWiki core or MediaWiki extensions, you must have read How to become a MediaWiki hacker to understand the infrastructure and workflow.
Potential tasks to work on
The following sections describe a few example areas in which you can contribute, but you are not limited to these areas!
If the software project uses Wikimedia Phabricator, the upper right corner of a task shows the project 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 core and extensions
Wikidata
Ask your general development questions on the Wikidata mailing list, the #wikidata IRC channel and on the wiki.
VisualEditor
Ask your general VisualEditor development questions on the wikitech mailing list and the #mediawiki-visualeditor IRC channel.
Discovery / Search
Ask your general development questions on the Discovery mailing list and on the #wikimedia-discovery IRC channel.
Skins
Basic knowledge of CSS and PHP is helpful.
Check the project page in Phabricator for more information on each skin and contact information.
Growth
Ask questions on the #wikimedia-collaboration IRC channel.
MediaWiki core
It is complex, written in PHP, and some areas might not have clear maintainership.
Ask your general development questions on the wikitech mailing list and the #wikimedia-dev and #mediawiki IRC channels.
Semantic MediaWiki
→ Potential tasks for new contributors
Standalone projects
Pywikibot
Ask your general development questions on the Pywikibot mailing list and the #pywikibot IRC channel.
Mobile Apps
For Wikipedia: Read the general development information and ask your questions on the Mobile mailing list and the #wikimedia-mobile IRC channel.
→ Potential tasks for new contributors: Android Wikipedia application
→ Potential tasks for new contributors: iOS Wikipedia application
For Commons: Read the general development information and ask your questions on the Commons App mailing list.
→ Potential tasks for new contributors: Android Commons application
Huggle
Data Engineering
Ask your general development questions on the Analytics mailing list.
Cross-project areas
Documentation
Design
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.
Strings
Also, many messages are unclear and require better documentation.
Missing documentation can also be added by 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.
And many more…
If you have any trouble or specific questions, please ask for help in one of our support places.
See also
- New Developers — Information for newcomers in the Wikimedia technical space, including Wikimedia software projects which offer mentors. Recommended for new contributors.
- How to become a MediaWiki hacker — For hacking on the core MediaWiki project or MediaWiki extensions.
- How to contribute — Learn about more ways how you can contribute to MediaWiki and the free culture community (e.g. translation, documentation, etc.)