71–80 of 147 posts
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.
Github is also well known and has issues, PRs and a CI all integrated into one, while with Phabricator each of these are either a self-host Jenkins (again, friction) or in a totally different/confusing location.
It's sad to see a tech company that many liked go, but hopefully this means the higher ups will reconsider Phab usage in my company :)
Earlier quoted context omitted.
Gerrit is solid: https://www.gerritcodereview.com/
It'd be nice if it had a tightly integrated issue tracker and CI.
Phabricator had seemed to be the only good product in this space when I had looked; what are people even using instead? (I guess they just put up with GitHub :/.)
Most of the stuff that Phabricator was used at our company is now done in (self-hosted) Gitlab. I think the only thing that's still actively there is credential management, and I can only imagine there are better solutions for that than Phabricator.
Earlier quoted context omitted.
being LAMP stack doesn't make software bad or otherwise more likely to fail commercially. The whole web (excluding some older perl/cgi-bin stuff) was built on it before Rails became popular.
Being LAMP is a sign of a good project that probably will work out of the box. Remember the P was for PHP or Perl.
Or Python.
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.
All the big companies have their own private fork resulting in zero contributions to the main project.
Earlier quoted context omitted.
And upstream made it pretty clear that they weren't interested in contributors or building a community :( https://secure.phabricator.com/book/phabcontrib/article/cont... > 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 c…
epriestly has a weird sense of humor. The "trials" were probably sending him a friendly email. (I worked at FB at the same time as him)
Doesn't GPL seem more palatable now? All the big companies have their own private fork resulting in zero contributions to the main project.
Maybe you're thinking of AGPL? That seems as likely to lead to no adoption as adoption with code contributions.
Earlier quoted context omitted.
It does an excellent job handling stacks! You may be mistaking it for Phabricator, which defaults to squashing.
I suspect that JoshTriplett is complaining about the `amend` workflow required to update a single gerrit patch with revisions. If you're used to the GitHub pull request style, you'd be more likely to make a small commit and add it to the request. In gerrit that approach results in a separate patch for review, which isn't what such a person would want. (Personally, I've come to appreciate gerrit's model for strongly e…