Live data from Hacker News

Phacility is winding down, Phabricator no longer actively maintained

admin.phacility.com

81–90 of 147 posts

Re: Phacility is winding down, Phabricator no longer actively maintained

#81
post #10
post #8

Earlier quoted context omitted.

Gerrit is solid: https://www.gerritcodereview.com/

The UI is atrocious, unfortunately.

Gerrit is a code review tool first, with code browsing not being a core focus.

GitHub and others are frequently code browsing tools first, with code review coming second. "Code hosting has look like GitHub" is unfortunately a common myopia.

Phabricator (from the little I used it) seems closer to Gerrit than other code hosting.

Re: Phacility is winding down, Phabricator no longer actively maintained

#82
It's interesting to see so many people with positive experiences with Phabricator - I work somewhere with a Phab install and onboarding new employees who've only ever used github/gitlab and branching workflows incurs a _significant_ cost. That, coupled with conduit being frustrating to develop against and lots of nice open source tooling basically being unusable without heavy modification due to assuming you're using a branching workflow has soured me on Phab. I'm hoping this can be used as additional justification to push us towards ... well... anything else. That being said, Herald is awesome and compared to basically any "modern" replacement, the UI is actually snappy and things don't get moved every 6 months for no goddamn reason (thanks Atlassian)

Re: Phacility is winding down, Phabricator no longer actively maintained

#83
I contributed to Phabricator a few times, and Evan was a pleasure to work with. I'm sorry to see it go but I hope for the best for Evan. I really hope this is a goodbye on to something great.

Phabricator will hold a great place in my heart as software written by a developer for developers that is well thought out, dog-fooded to the max, and fun.

My hope is that it can be well stewarded by a company into continuity. I wish I had the time to do so.

In short, thank you Evan and all those in the community for many years of wonderful software development.

Re: Phacility is winding down, Phabricator no longer actively maintained

#84
What I really like about Phabricator as a review tool:

* keyboard shortcuts to navigate through the changes

* ability to add a comment to multiple lines of code

* ability to suggest changes inline

* comments are saved as I type them, so an accidental tab close saves my work

* comments are submitted in batches when I choose to, not one-by-one after saving each one. Its's sooo useful, because it often happens that I ask a question about some piece of code and upon further reading I find the answer, so I can delete the question before submitting all the comments and the author won't be bothered by it

If anyone knows of a feview tool with similiar set of features, please please let me know :)

When it comes to task management in Phab, I like how the tasks can be arranged in a dependency tree. We have our "todo" view set up so it only shows tasks without dependencies and sorted by prioroty, so the work on the project self-organizes

Re: Phacility is winding down, Phabricator no longer actively maintained

#85
post #13

To clarify: this applies not just to phabricator-dot-com, but Phabricator the software: https://github.com/phacility/phabricator/commit/9ceb66453501... 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…

I think Blender and KDE uses Phabricator as well.

Lubuntu uses it. We'll have to get this sorted out at some point.

Re: Phacility is winding down, Phabricator no longer actively maintained

#86

As others have mentioned, this is a shame. I found the Phabricator review model much more flexible and easy to work with than GitHub and Github-clone workflows. It's basically the traditional ultra-scalable mailing-list + patches workflow, but with very nice tooling and UI on top. I'm going to miss it when I leave FB some day.

as an addon, I'd love to see more organizations try to tackle this problem without just lifting the flawed GitHub model.

I have no experience with phabricator but it sounds like sourcehut - are you familiar with that one?

Re: Phacility is winding down, Phabricator no longer actively maintained

#87
We've been using Phabricator for several years and just recently started to use Gitlab in parallel. One of the main reasons was Phabricator's confusing and esoteric use of "spaces" for access control that made it hard to include external developers on projects. On the other hand the Phabricator GUI is much less confusing than Gitlab.

Re: Phacility is winding down, Phabricator no longer actively maintained

#88
Phabricator has been a huge part of my career. Having spent the past 11ish years maintaining phabricator installs this really hit me hard. Fwiw phabricator is very stable and maintainable code. I would be happy to work with anyone who is interested in collaborating on a community maintained fork.

Re: Phacility is winding down, Phabricator no longer actively maintained

#89
post #13

To clarify: this applies not just to phabricator-dot-com, but Phabricator the software: https://github.com/phacility/phabricator/commit/9ceb66453501... 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…

FB's phabricator went its own way long ago. I imagine this has exactly zero impact on their day to day. Put it this way: the last time I saw it, they still had the "clowncopterize" button. Try finding that anywhere else.

That sounds fun! What did it do?

Re: Phacility is winding down, Phabricator no longer actively maintained

#90
post #87

We've been using Phabricator for several years and just recently started to use Gitlab in parallel. One of the main reasons was Phabricator's confusing and esoteric use of "spaces" for access control that made it hard to include external developers on projects. On the other hand the Phabricator GUI is much less confusing than Gitlab.

There are other ways besides spaces to control access in a fine grained way by using projects as access control lists and policies on the areas you want to restrict.
Post reply on HN