Conversation

Phab saved our asses a ton of times. My boss would ask: "Why did we decide not to implement this feature? A customer is asking." And within 5 mins I could go from git blame to the specific task documenting why we chose not to implement something. Everything was linked.
1
The interface was also incredible for tracking development across many devs. I remember an intern sitting on a couch, writing his internship report simply by going through his Phab activity. And I remember saving Fridays for reviewing the activity of EVERY dev in my org.
1
1
The only knock against Phab was the lack of good CI support. And I think Gitlab and Github may have finally caught up. Phabricator was truly incredible software. I'm very sorry to see it go.
2
1
(Now I'm debating shutting down my account with them, and digging up the old Ansible playbook I wrote to install Phabricator on a server. Not sure if I want to run my own instance forever, though ...)
1
Replying to
That solves for the hosting part: what will be more critical is longer term maintenance of project? I'm curious to see what will happen with bigger institutional users (wikimedia, dropbox, Uber, etc)
1
1
Replying to
I’m actually ok with that — Phabricator has been rock solid for me for years and years (ran a hosted install for about 5 years at prev company, and it’s still going strong). I’m assuming it’s ‘done’ software for my use case, and willing to stick it out for a few more.
1
Show replies