This is unexpected. Many companies, among them as well-resourced as Facebook, use Phabricator. I wonder if it will be forked soon by some party interested in keeping it around. OTOH it looks like none such party exists, because the public sources have not been updated literally for years. Maybe everyone interested just runs their private fork :(
Phabricator should be reasonably easy to self-host anyway.
What I remember of Phabricator when I used it years ago was the very confusing naming of things, that didn't improve the user experience. It did have a nice command line tool to help you in your workflow.
I think Phabricator's heyday was during a time when everyone was trying to formalize their workflow, another project of that time was git flow.
Facebook’s diff tool looked similar maybe 5 years ago but there’s been constant improvements to it in that time. There was a dedicated team maintaining and improving it. Today it bears only a passing resemblance to Phabricator.
GP’s claim that Facebook uses Phabricator is an overstatement.
> Phabricator should be reasonably easy to self-host anyway.
It's a bit of a mixed bag compared to other self-hostable applications. There are a lot of moving parts, and the initial setup requires 60 different unique databases. It has a handful of background daemon-like processes that occasionally get wedged.
But, overall, there are some really interesting pieces of architecture in it, it's a really big project, and it does a lot of things pretty well.
5-10ish years ago I stood up both gitlab and phabricator. The latter was much easier. I really, really liked phabricator, though much of it's advantages went away when using DVCS; for SVN, it's command line tools were just a joy to use by comparison.
> To contribute to the Phabricator upstream, you must first pass a series of ancient trials and be invited to register an account in the ancestral homeland of Phabricator, here on secure.phabricator.com. The nature and location of these trials is a closely guarded secret.
Yeah, we already switch to Gitlab for code review. But the task management utility in Phabricator are far superior to Gitlab, so it's a bit complicated to switch to Gitlab for now.
There has been three big reasons why we are trying to switch from phab to Gitlab:
* Upstream wasn't very interested in external contributions or hearing our suggestions
* arcanist was a real pita to use for new contributors. Switching to gitlab really increased the number of occasional contributors.
* Setting up CI with Phabricator to run on Diff (the Phabricator equivalent to merge request) was not easy.
This is unexpected. Many companies, among them as well-resourced as Facebook, use Phabricator. I wonder if it will be forked soon by some party interested in keeping it around. OTOH it looks like none such party exists, because the public sources have not been updated literally for years. Maybe everyone interested just runs their private fork :(
Phabricator should be reasonably easy to self-host anyway.