Phabricator

Phabricator
Name	Phabricator
Developer	Phacility (original), community forks
Initial release	2009
Programming language	PHP
Operating system	Unix-like
License	Apache License 2.0 (original); assorted forks vary

Phabricator is an open-source suite of web-based software development collaboration tools originally developed by a private company and later maintained by a distributed community. It provides integrated services for code review, repository hosting, task tracking, continuous integration orchestration, and developer communication. The platform attracted attention from technology companies, research organizations, and open-source projects for its modular architecture and strong focus on code review and project workflow.

History

Development began inside a private engineering organization associated with Facebook, led by engineers who later formed a separate entity called Phacility. Early iterations drew on practices from Mercurial and Subversion users at internet companies. Public visibility increased following adoption by organizations such as Facebook and Mozilla Foundation adopters, and the project evolved through contributions influenced by practices at Google, Amazon (company), and Twitter. Phacility provided hosted instances and commercial services until organizational changes and funding constraints prompted a transition toward community stewardship. The decline of corporate sponsorship led to several independent forks and mirrors maintained by contributors from projects like KDE, GNOME Foundation, FreeBSD, and Debian.

Architecture and Components

The architecture centers on a monolithic PHP application designed to run on Linux distributions and interoperate with multiple version control systems. Core components include a web frontend, a relational datastore typically using MySQL, and daemons for asynchronous tasks. Integration points were created for Git, Mercurial, and Subversion repositories, enabling repository hosting and change import. Authentication and identity features connected to LDAP directories and single sign-on providers such as OAuth (protocol) implementations used by GitHub, GitLab, and enterprise identity systems at organizations like Red Hat and IBM. The system exposed APIs and extension points modeled after practices in Apache HTTP Server module ecosystems and Django-style web frameworks, allowing projects such as LLVM and Free Software Foundation forks to add functionality.

Features and Workflow

Phabricator combined task tracking, code review, repository browsing, and continuous integration triggers into a single workflow. The Differential application provided pre-commit and post-commit code review comparable to review tools used at Google and Microsoft, while the Herald rule engine supported automated rules similar to Jenkins build triggers and Travis CI notifications. Maniphest served as an issue tracker adopted by teams in companies like Stripe and Airbnb for planning and bug triage, and Phriction offered wiki-style documentation used by contributors from projects such as Blender and LibreOffice. Audit and Herald components facilitated security and compliance patterns akin to processes at NASA and European Space Agency, and integrated dashboards echoed approaches used by Atlassian products. Notifications, inline comments, and review blocking mirrored social-code-review practices found at GitHub and enterprise workflows at Microsoft Azure DevOps.

Deployment and Hosting

Deployment typically targeted Unix-like servers running Debian, Ubuntu, or CentOS and used NGINX or Apache HTTP Server with PHP-FPM. Operators often combined Phabricator with database clusters employing Percona or MariaDB and caching layers using Memcached and Redis. Continuous integration integrations and webhooks interfaced with systems like Jenkins, Bamboo, and CircleCI for build orchestration used by engineering teams at Dropbox and Box. Administrators from academic institutions such as MIT and Stanford University customized deployments to integrate with campus LDAP and SAML providers similar to setups used by Harvard University and University of California, Berkeley.

Community and Governance

After the original company ceased active stewardship, governance shifted to a dispersed community of maintainers, contributors, and independent forks. The stewardship model paralleled transitions seen in projects like OpenOffice to Apache Software Foundation and forks such as LibreOffice. Contributors included developers affiliated with Mozilla Foundation, KDE, and corporate engineering groups from Google and Stripe. Decision-making followed norms similar to other open-source communities maintained on platforms like GitHub and GitLab, with patch review, mailing lists, and IRC channels echoing community practices at Apache Software Foundation incubations and Linux Foundation projects.

Adoption and Notable Users

Adoption spanned startups, mid-size companies, and open-source projects. Notable users included engineering groups at Facebook in early stages, and later adopters such as Mozilla Foundation, Dropbox, and various academic labs at Carnegie Mellon University and University of Cambridge. Forks and alternative hosted offerings were adopted by infrastructure teams at Red Hat and contributors from FreeBSD and OpenStack. Several open-source ecosystems, including KDE and GNOME Foundation, evaluated or used forks for code review and task management, while smaller technology firms and research groups in institutions like Lawrence Berkeley National Laboratory leveraged the platform for reproducible development workflows.

Category:Software