Phabricator project: #Phabricator


(Redirected from Feature requests)
Jump to: navigation, search

Phabricator is an open-source software development platform used for project management, bug reporting, feature requests, and code review in an integrated fashion.

For a Wikimedia-centric overview, watch the Tech Talk The Very Basics of Phabricator. Bugzilla users are encouraged to read our Phabricator versus Bugzilla comparison.

Get started! First missions include

Check our Phabricator Help. Your questions are very welcome.

For Phabricator support and camaraderie, join #wikimedia-devtoolsconnect.[edit | edit source]

Wikimedia Phabricator overview.

After a favorable request for comment, we are deploying to replace Bugzilla, RT, Trello, Mingle, Gerrit, and gitblit. Why?

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

Weekly update / maintenance window[edit | edit source]

Phabricator doesn't have releases, and therefore it is up to us to decide how close do we want to follow the upstream version. There is a weekly window for updates and other maintenance tasks on Wednesdays at 15:00 UTC (check your timezone) and users will get redirected to Phabricator/Maintenance. We don't update Phabricator every week, but we reserve us the right to do it. The expected downtime during this window goes from 0 to 30 minutes.

Migration timeline[edit | edit source]

Beware, the Phabricator team may change this sequence as plans evolve (although we try not to). If you need more details, you can find them at T174 - Launch Wikimedia Phabricator Day 1.

  1. YesY Done Deployment of (project)
  2. YesY Done Migration of data from to
  3. YesY Done New test instance in Labs open to everyone, blocked by
  4. YesY Done open to all Wikimedia users
  5. YesY Done Test instance containing Bugzilla reports automatically migrated
    • YesY Done end of Bugzilla preview feedback period, announcement of Bugzilla migration date.
  6. YesY Done, 2014-11-21: Bugzilla migration (1-4 days downtime, see detailed timeline), blocked by
  7. Incomplete Partially done, 2014-12-18 00:00UTC-08:00UTC: Phabricator RT migration: RT migration (8 hours downtime of Phabricator; blocked by
  8. In progress In progress Define main tasks (epics) for code review in Phabricator
  9. In progress In progress, expected during October or November: Burndown charts & migration from Scrumbugz
  10. To do To do, expected before the end of 2014: Total migration from Mingle
  11. To do To do, expected before the end of 2014: Total migration from Trello
  12. To do To do, expected before the end of 2014: Proof of concept of code review in Phabricator
  13. To do To do, before 2015-03-31? Total migration from gitblit
  14. To do To do, before 2015-03-31? Total migration from Gerrit
  15. To do To do, before 2015-06-30? Total migration from Jenkins

Get started[edit | edit source]

Access to is open, but please be aware of the migration timeline and the fact that the site might be entirely down during the RT and Bugzilla migrations.

There is a test instance at Use it to learn and experiment, not for serious work.

Learn more about Phabricator versus Bugzilla. You can also watch a screencast about handling tasks/bugs.

If you have questions, check the Help and the FAQ.

Get involved[edit | edit source]

We are working on the migration of several developer infrastructure services to one single Phabricator instance. It's a very exciting project! We welcome your help.

  • Learn to use Phabricator. Play and test in our Labs instance as much as you want.
  • You might want to watch the kick-off meeting of the Wikimedia Phabricator Day 1 project.
  • Bugzilla, RT, Trello, and Mingle users are welcome to the Phabricator project. Your help is welcome anywhere, but especially in the tasks that are blocking Day 1.
  • Git and Gerrit users are welcome to the Code Review in Phabricator project. We need help learning about the possibilities of Phabricator in this area: what is missing, what exists in a different way, what is remarkably interesting, which are the blockers that should be reported upstream?

Developers[edit | edit source]

As a PHP developer, you're welcome to contribute enhancements and new features upstream. Learn more at Phabricator/Code.

See also[edit | edit source]