Quim Gil

Phabricator is an open source software development platform used for project management, bug reporting, and code review in an integrated fashion. Wikimedia has about 500 regular contributors developing MediaWiki plus hundreds of extensions and related tools. We are deploying https://phabricator.wikimedia.org to replace Bugzilla, RT, Trello, Mingle, Gerrit, gitblit, and Jenkins. This is the biggest and most complex Phabricator migration we are aware of, and we want to share our first-hand experiences with other free software projects.

Why such a big change? All the tools we are/were using kind of work/ed. However, we felt that the cocktail of tools was slowing us down, becoming also an obstacle for new contributors. In more detail:

• The volume and complexity of our software projects keeps increasing; MediaWiki and Bugzilla fall short for project management.
• Wikimedia Foundation teams were increasingly using Mingle and Trello, 3rd party commercial services that are alien to the Wikimedia community and principles. This was creating a divide. Wikimedia Germany was trying Scrumbugz, a one-man OSS project barely maintained.
• Overlap, duplication, and actions falling between the cracks increased.
• To mitigate this problem, we created more tools to synchronize information between services (like "Bingle", "Bugello" or Gerrit notifications in Bugzilla). They needed to be maintained (i.e. when one service is upgraded and its API interface has changed).
• Contributing to Bugzilla (Perl) and Gerrit (Java) is complex for us (PHP, and Phabricator is written in PHP), while there is no way to contribute code to proprietary Mingle and Trello.
• The current setup brings overhead and annoyance to key developers: Senior developers having to use heavily Gerrit, Bugzilla, and Mingle/Trello. New contributors, most of them arriving with GitHub-like expectations.

As we write these lines, this is an ongoing work. Learn more about the Wikimedia Phabricator timeline and other project details at https://www.mediawiki.org/wiki/Phabricator

10 proposals to get you started in the MediaWiki community

Annoyed by some detail? Suffering some bug? Missing some feature? Having a cool idea? Wondering what comes next? Here you have the top 10 activities that you can start right here right now.

You use Wikipedia. Maybe you donate to Wikipedia. Maybe you even edit Wikipedia. Or any other Wikimedia project: Commons, Wiktionary, Wikiversity... Since you are in FOSDEM chances are that you know what is MediaWiki. Maybe you are using it in some website or intranet. Maybe you even are a MediaWiki admin. Or maybe you even installed it once...

Anyway, we just came here to say that being a Wikipedia reader AND a FOSDEM attendee you simply qualify as technical contributors to one of the most amazing collaborative projects happening now. Annoyed by some detail? Suffering some bug? Missing some feature? Having a cool idea? Wondering what comes next? Here you have the top 10 activities that you can start right here right now:

(The list will go through 10 examples of tasks for developers, testers, designers, sysadmins, doc writers, and even product and marketing people! A page in mediawiki.org will list these tasks and point to the right places to get you started).

Now you saw the dark side. You smelled the red pill. No matter what you do (or don't do), reading Wikipedia will never be the same.