Good first bugs/fr

Cette page fournit une liste de petits bugs et de petites fonctionnalités manquantes qui gênent les utilisateurs et qui sont relativement facile à résoudre pour un nouveau codeur MediaWiki. C'est une bonne façon pour commencer à se familiariser avec la base du code MediaWiki. Vous devez d'abord avoir lu la section "Pour démarrer" de Comment devenir un geek MediaWiki pour comprendre l'infrastructure, les flux de travail et les attentes en communication.

Bogues potentiels à travailler
Les sections suivantes décrivent quelques exemples de domaines dans lesquels vous pouvez contribuer, mais vous n'êtes pas limités à ces domaines !

Dans le coin supérieur droit d'une tâche (rapport de bogue) de Phabricator vous pouvez voir le produit et le composant où le problème est localisé. Cela vous donne une indication sur le dépôt Git où le code est situé, et sur l'équipe de développement que vous pouvez contacter si vous souhaitez en discuter d'une manière «plus large» (sous forme de commentaires dans les rapports de bugs qui devraient de préférence se rapporter au problème spécifique décrit uniquement dans le rapport).

Documentation

 * Liste des rapports de bogues ouverts et des demandes d'amélioration liées à la documentation avec le mot-clé "facile"

Pywikibot
PyWikibot est un "framework" à base de Python qui permet d'écrire des robots pour MediaWiki. Posez vos questions concernant le développement général sur la liste de diffusion Pywikibot et le canal IRC #pywikibot.


 * Liste des rapports de bogues ouverts les plus faciles de Pywikibot et demandes d'amélioration.

Multimédia
Posez vos questions générales concernant le développement Multimedia sur la liste de diffusion multimédia et le canal IRC #wikimedia-multimedia.


 * Liste des rapports de bugs ouverts les plus faciles concernant le multimédia et demandes d'amélioration.

Applications Mobiles
Il existe de nombreuses applications pour les appareils mobiles (Android, iOS, Windows Phone, ...) pour accéder aux "wikis" Wikimedia. Lisez les informations de développement générales et posez vos questions sur la liste de diffusion Mobile et le canal IRC #wikimedia-mobile.


 * Liste des rapports de bogues ouverts les plus faciles des applications mobiles et les demandes d'amélioration.

Reading
The reading team builds the software that serves our readers. We also manage the mobile web experience. Read the general development information and ask your questions on the Mobile mailing list and the #wikimedia-mobile IRC channel.


 * List of open easy reading web tasks

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.


 * List of open easy Wikidata bug reports and enhancement requests

Huggle
Huggle is a desktop application for dealing with vandalism on Wikimedia projects, written in C++.


 * List of open easy Huggle bug reports and enhancement requests

Browser Tests & Quality Assurance
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.


 * List of open easy Browser Test 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.


 * List of open easy Language Engineering 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.


 * List of 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.


 * List of open easy Parsoid bug reports and enhancement requests

Discovery / Search
The Discovery team builds the path of anonymous discovery to a trusted and relevant source of knowledge. Ask your general development questions on the Discovery mailing list and on the #wikimedia-discovery IRC channel.


 * List of open easy Discovery / Search 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.


 * List of 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.


 * List of open easy design bug reports and enhancement requests

Skins
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.


 * List of open easy skin 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).


 * List of open string change bug reports and enhancement requests (under "Blocked by")

Collaboration
The Collaboration team mainly works on Echo and Flow.

Ask questions regarding Collaboration team projects on the #wikimedia-collaboration IRC channel.


 * List of open easy Collaboration team bug reports and enhancement requests

MediaWiki
MediaWiki is the core software which provides basic wiki functionality. 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.


 * List of open easy MediaWiki bug reports and enhancement requests

Phlogiston
Phabricator is used by Wikimedia for project management, software bug reporting and feature requests. Phlogiston is a set of SQL, Python, and R scripts to report on Phabricator data, particularly burnup reports and forecasting.


 * List of open easy Phlogiston bug reports and enhancement requests

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:


 * List of open easy bug reports and enhancement requests

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

Voir aussi

 * — 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
 * Oldest open changesets in Gerrit — your help reviewing them is welcome