From mediawiki.org
Jump to navigation Jump to search
This page is a translated version of the page New Developers and the translation is 71% complete.
Outdated translations are marked like this.
Other languages:
Bahasa Indonesia • ‎Deutsch • ‎English • ‎català • ‎español • ‎français • ‎polski • ‎português • ‎português do Brasil • ‎suomi • ‎русский • ‎עברית • ‎العربية • ‎বাংলা • ‎中文 • ‎日本語

此页面是新维基媒体开发人员的简单指导登录页面。 它是入门新开发者计划的一部分。







  1. 选择一个软件项目
  2. 配置您的开发环境
  3. 选择并解决任务(编写和测试代码)
  4. 提交您的代码更改



Wikimedia在许多不同领域有数百个软件项目。 如果你想了解概况,请查看这些幻灯片

每个软件项目的维护者都可以很自由地选择他们喜欢的基础结构。 一般来说,基本上所有的软件项目都有

  • 一种任务追踪工具,用于报告、管理和讨论软件bug和改进请求。例如Wikimedia Phabricator、GitHub或Sourceforge。
  • 一个源代码库,源代码可以复制到每个人的代码存储库。例如Wikimedia Git/Gerrit、GitHub或Sourceforge。
  • 一个代码检查工具,用于讨论和改进建议的代码更改(patches)。例如Wikimedia Git/Gerrit、GitHub或Sourceforge。一旦你提出的patch很好,并被合并到代码库中,你的代码更改将对每个人都可用。(你可以在这里阅读更多关于代码审查的良好实践。
  • 讨论软件项目和/或接受帮助和支持的场所。这些地方可以是邮件列表,或IRC聊天频道,或wiki页面,或其他地方。具体的位置取决于每个项目。你也可以在他们的用户页面上通过“电邮联系该用户”联系特定的用户,但是要注意私下问的问题不会帮助到他人。

在任何时候,如果你遇到问题或需要帮助,请提问。 如果你想在合适的地方提出好的问题,我们建议你阅读“反馈、问题和支持”部分。


这是推荐的开始方式。 选择下列项目之一,并按照项目的帮助文档配置您的开发环境,选择一个任务,解决该任务,并提交您的代码更改以供检查:










Wiki Education Dashboard




ORES highlights problematic edits

为Wikimedia项目提供机器学习服务的web服务和API。 机器预测用于发现破坏行为、衡量条目质量和执行其他wiki工作。




Logo Pywikibot


A Python library and collection of scripts that automate work on MediaWiki sites.

Logo AfC Helper Script

Screenshot of the AfC Helper Script in use

A user script to review draft articles on Wikipedia.

Logo VideoCutTool


A tool to edit the videos on Wikimedia Commons.

Are you a maintainer and want your project to be included in the list of software projects above? Find out more and join!


Apart from the recommended software projects above, there are more ways to choose a project or task to work on:

Logo 外展计划

Wikimedia offers internships in programs such as Google Summer of Code and Outreachy.

Logo Good first tasks

There are many single tasks (across many software projects) which are suitable for newcomers.
However, you are more on your own here: We cannot guarantee that mentors are available or that your proposed patches will receive fast reviews.


  • Developer hub: Resources to more documentation and information for established Wikimedia developers.
  • There are also several email lists for discussion of Wikimedia software.
  • Wikimedia tutorials: An index of tutorials that feature various languages, APIs, and frameworks in the Wikimedia technology stack.


  • 如何贡献列出了许多非技术领域的贡献方式。

Some general communication tips

  • Do your research first: When you decide to work on a task, you are expected to do some basic research yourself first: Look at the code, try to get some understanding what it is supposed to do, read related documentation, try to find the probable place(s) where you need to make code changes. For a general overview, please read the Basics to know.
    • In a Phabricator task, see the project tags in the side bar to find out which code repository a task is about.
  • Ask and discuss in the best place:
    • In Phabricator tasks, discuss only specific questions about the topic of that very Phabricator task. General technical questions (e.g. how to set up a development environment or problems with Gerrit) are off-topic in Phabricator tasks.
    • For general technical questions, ask the broader Wikimedia community and use generic channels like IRC chat or mailing lists. (If you take part in an outreach program, then you can also use Zulip's technical-support stream.)
    • If you take part in an outreach program, then Zulip is for discussing questions about the outreach programs themselves.
  • Ask good questions: "Can you give me more info?", "Please guide me", "Please tell me how to start" are not good comments to start with: The more specific your questions are, the more likely somebody can answer them quickly. If you have no idea at all how to fix the bug, maybe that bug is not (yet) for you – consider finding an easier one first.
  • Provide context: When asking, explain what you want to achieve, and what you have tried and found out already, so others can help at the right level. Be specific – for example, copy and paste your commands and their output (if not too long) instead of paraphrasing in your own words. This avoids misunderstandings. Use specific titles and subject lines ("Proposal draft" or "Need help" is not specific).
  • Use inclusive language: Don't assume anyone's gender identity ("guys", "madam", "sir"). Use the name of the person instead.
  • Ask in public: Do not send private messages if your conversation topic is not secret. Private messages do not help others.
  • Be patient when seeking input and comments, especially during weekends and holidays.
    • On IRC, don't ask to ask, just ask: most questions can be answered by other community members too if you ask on an IRC channel. If nobody answers, please try again at a different time; don't just give up.
    • Do not ask people immediately for code review in a separate message. People receive Gerrit and Phabricator notifications.
  • Keep conversations readable: When you reply in Zulip, in Phabricator tasks, or on mailing lists, please avoid unneeded quoting of a complete previous comment. Provide sufficient context and keep threads readable.
  • Follow the code of conduct for Wikimedia technical spaces.
  • When you plan to work on a Phabricator task:
    • No need to ask for permission: Usually there is no reason to ask if you can work on something or if somebody could assign a task to you. There is no authority who assigns tasks or who needs to be asked first.
    • You do not need to announce your plans before you start working on a task but it would be welcome. At the latest when you are close to proposing a patch for a task, it is good to announce that you are working on it, so that others don't duplicate work: If nobody else is already assigned, set yourself as task assignee by using the Add Action… → Assign/Claim dropdown.
    • Tasks with existing patches:
      • If a task already has a recent patch in Gerrit, choose a different task to work on instead – avoid duplicating work.
      • If an existing patch in Gerrit has not been merged and has not seen any changes for a long time, you could also improve that existing patch, based on the feedback in Gerrit and in the task.
    • When your plans or interests change: If you don't work on a task anymore, please remove yourself as the assignee of the task, so others know that they can work on the task and don't expect you to still work on it.

By communicating clearly and early you get attention, feedback and help from community members.