Phabricator

---

Phabricator

---

2014 Project management tools review

---

• Phabricator migration planning
• Help
• FAQ

---

• Blockers and Migration prep → in progress
• Migration plan → in progress

---

Past steps:

1. Y Share your needs & workflow
2. Y Consolidated requirements
3. Y Options (discuss)
4. Y RFC

---

See also

---

• Current project management tools
• 2012 Gerrit evaluation

---

Edit

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

The migration to Phabricator is work in progress. See the timeline below for more information.

Get started

Play media

Wikimedia Phabricator documentation overview

Play media

Intro to Wikimedia Phabricator

Play media

Introduction to phab-01.wmflabs.org

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

You can also watch a screencast about handling tasks/bugs.

First missions include

• Creating your account
• Creating a task
• If you maintain projects: Creating a project and learning about project management in Phabricator.

• Etiquette

If you have questions, check the Help and the FAQ. Your questions are very welcome.

For Phabricator support and camaraderie, join #wikimedia-devtools^connect.

There is a test instance at phab-01.wmflabs.org. Use it to learn and experiment, not for serious work.

Get involved

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. Check out the documentation and short videos on Phabricator/Help.
• Git and Gerrit users are welcome to the Gerrit-Migration 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?

Report bugs and feature requests

We have two different projects to handle Phabricator related tasks:

• Phabricator contains all the tasks specific to Wikimedia Phabricator: our processes, aspects related to migration of Wikimedia data, local customizations...
• Phabricator-upstream is used for tasks that should be handled upstream at https://secure.phabricator.com: generic Phabricator bugs and feature requests which are not specific to Wikimedia's Phabricator instance.

See the Wikimedia Phabricator bug workflow for more details.

Developers

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

Weekly update / maintenance window

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 5:00PM Pacific (Thursday Midnight, 0:00 UTC) (check your timezone) and users will get redirected to Phabricator/Maintenance. We don't necessarily update Phabricator every week, but we reserve this window to use as needed, usually twice per month, depending on the urgency of outstanding bugs fixed upstream. The expected downtime during this window is between 0 and 30 minutes.

Migration timeline

Beware, the Phabricator team may change this sequence as plans evolve (although we try not to).

1. YDone Deployment of https://legalpad.wikimedia.org/ (project)
2. YDone Migration of data from fab.wmflabs.org to phabricator.wikimedia.org
3. YDone New test instance in Labs open to everyone, blocked by
4. YDone phabricator.wikimedia.org open to all Wikimedia users
5. YDone Test instance containing Bugzilla reports automatically migrated
   • YDone end of Bugzilla preview feedback period, announcement of Bugzilla migration date.
6. YDone, 2014-11-21: Bugzilla migration (1-4 days downtime, see detailed timeline), blocked by
   • YDone Community review of the Bugzilla migration test instance (two weeks)
   • YDone Bugzilla to Phabricator import script
   • YDone Elasticsearch (but temporarily reverted)
   • YDone Move Bugzilla to old-bugzilla.wikimedia.org as a read-only instance
   • YDone Automatic redirects from Bugzilla reports to Phabricator tasks
   • YDone Wiki templates for Bugzilla pointing to Phabricator
   • YDone Gerrit plugin to sync tasks with code reviews
   • YDone IRC bots reporting Phabricator activity
   • YDone How to organize projects
   • YDone How to claim Bugzilla reports
   • YDone Documentation for Bugzilla users
   • YDone Communication plan
   • YDone Approval from Wikimedia Foundation Engineering management
   • YDone Reminder: Bugzilla migrated projects and tasks must be Visible To Public
7. YDone except for minor queues, 2014-12-18 00:00UTC-08:00UTC: Phabricator RT migration: RT migration (8 hours downtime of Phabricator; blocked by
   • YDone Interaction with external users via email
8. YDone Burndown charts & migration from Scrumbugz
9. In progress Define main tasks (epics) for code review in Phabricator
10. In progress, before 2015-06-30? Total migration from Mingle; cf. T825
11. To do, before 2015-06-30? Total migration from Trello; cf. T825
12. To do, before 2015-07-31? Proof of concept of code review in Phabricator
13. To do, before 2015-07-31? Total migration from gitblit
14. To do, before 2015-12-31? Total migration from Gerrit
15. To do, before 2015-12-31? Total migration from Jenkins

See also

• phabricator.wikimedia.org permissions
• Subpages (/Bots, /Help, /Maintenance, /Project management, /Security, …)
• wikitech:Phabricator (technical information for administrators)