Phabricator

Phabricator is an open-source software development platform. In Wikimedia, Phabricator is used for project management, bug reporting and feature requests (see ), and in the future also for code review in an integrated fashion.

The phab-migration>Phabricator/Migration|migration to Phabricator is mostly complete. See the timeline page for more information.

Get started


If you have questions, check the phab-help>Phabricator/Help|Help page. Your talk-phab>Talk:Phabricator/Help|questions are very welcome.

You can also watch a screencast about [https://plus.google.com/events/cm38slj29u0pb65iilcrb3vgn88 handling tasks/bugs].

First missions include


 * phab-account>Phabricator/Help#Creating your account|Creating your account
 * phab-task>Phabricator/Help#Creating a task|Creating a task
 * If you maintain projects: phab-projects>Phabricator/Creating and renaming projects|Creating a project and learning about phab-manage>Phabricator/Project management|project management in Phabricator.


 * 1>Bug management/Phabricator etiquette|Etiquette


 * Learn to use Phabricator. Play and test in [https://phab-01.wmflabs.org/ our Labs instance] as much as you want. Check out the documentation and short videos on .

See the Wikimedia Phabricator bug workflow for more details.
 * Report bugs and features in the Phabricator software itself in the phab-tag>phab:tag/phabricator/</>|Phabricator project.

For Phabricator support and camaraderie, join <tvar|irc></>.

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) ([<tvar|timezone>http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150603T17&p1=224&ah=1</> check your timezone]) and users will get redirected to <tvar|phab-maint>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.