News for hackers. Stuff that matters.
Re:Moving to GitLab by judge2020 on Saturday December 01, 2018 @09:20PM (#18580375)
Note: this is about moving from Phabricator to GitLab, not GitHub to GitLab.

GHC Discussion from November about moving to GitLab/moving away from Phabricator: https://mail.haskell.org/pipermail/ghc-devs/2018-November/01...

Re:Moving to GitLab by the_common_man on Saturday December 01, 2018 @09:58PM (#18580535)
Does anyone know what did not work out with phabricator?
Re:Moving to GitLab by meestaplu on Sunday December 02, 2018 @01:00AM (#18581056)
Ben Gamari's October 30 email (https://mail.haskell.org/pipermail/ghc-devs/2018-October/016...) to the ghc-devs list proposed considering alternatives to Phabricator and outlines reasons that Phab wasn't working.

A summary of the problems outlined in the email:

* Lack of options for support from Phacility

* Free/open source components of Phabricator feeling half-finished because Phacility has redirected development resources to paid features

* Issues with Harbormaster (Phabricator's half-baked CI system)

* Developer's prefer using regular Git to Phabricator's nonstandard workflow, which requires installation of the Arcanist command-line tool (written in PHP to manage patches.

Re:Moving to GitLab by edoceo on Sunday December 02, 2018 @01:37AM (#18581143)
> Phabricator's nonstandard workflow, which requires installation of the Arcanist command-line tool

I was just going to eval Phab for my team, your comment identified a deal breaker for us and you've saved me more than a few wasted hours. Thank you

Re:Moving to GitLab by munchor on Sunday December 02, 2018 @02:49AM (#18581308)
I am actually a big fan of Arcanist. It rather simplifies the Git workflow management. You simply develop new code in a separate branch from master, and use `arc diff` from said branch to start a Pull Request (called a "diff" in the Arc world). No need to use `git push` and manage upstream branches, simply rely on the diff abstraction. It has many great features including `arc diff --preview` which gives you a link to a preview of your PR so you can see what it looks like in the browser (much better than `git diff`).

Of course, there is a bit of a learning curve and most engineers already know the standard git workflow. That is a disadvantage of course, but only in the short term. If it's a short project, then I would recommend against it. However, if you're in it for the long run, arc is great.

I feel like the other points (CI, lack of support, etc.) much better show the weak points of Phabricator versus GitHub or GitLab.

Re:Moving to GitLab by lima on Sunday December 02, 2018 @05:07AM (#18581690)
Phabricator's nonstandard workflow and tooling is one of its distinct advantages - maybe give it a second thought.
Re:Moving to GitLab by IshKebab on Sunday December 02, 2018 @09:46AM (#18582490)
Arcanist is actually a reasonably nice tool. It is certainly far superior to opening pull requests in a web interface.

The only real downside I've found with using phabricator at work is the lack of a decent built in CI system. You can integrate it with external ones fairly well but that seems like something you shouldn't have to do.

Re:Moving to GitLab by lugg on Sunday December 02, 2018 @07:04AM (#18581985)
Please ignore the others in this thread.

Phabricator is basically cancer.

I'm partial to Gerrit if you're looking for a git native solution with branch, draft, patch, review, iterate workflows with proper merge/rebase handling.

It is a bit different from "GitHub flow" but mostly a big improvement in an organisation context (vs FOSS.)

Media wiki has the best docs but it's a bit dense.

https://mediawiki.org/wiki/Gerrit

This page below has a decent graphic and lots of quick examples to show you how powerful it is to work with git instead of gimping it with a wrapper.

https://mediawiki.org/wiki/Special:MyLanguage/Gerrit/Advance...

Re:Moving to GitLab by skrebbel on Sunday December 02, 2018 @08:05AM (#18582148)
> Phabricator is basically cancer.

I think you need a lessen in sensible writing. You don't like Phabricator, fine. It's not cancer. Not "basically" either.

Re:Moving to GitLab by lugg on Sunday December 02, 2018 @08:26AM (#18582202)
You don't like my casual use of the word cancer? Fine. Personally I feel like cancer was a relatively good approximation for the cancerous like changes you need to make to established industry workflows once you begin to use phabricator.

Would you have preferred I used the word infection? Virus? Aids?

Which one of those metaphors crosses the "sense writing" line for you?

Why does cancer?

Re:Moving to GitLab by barneygale on Sunday December 02, 2018 @08:55AM (#18582313)
Describing software as "cancer" is something I'd expect to see on 4chan or reddit, not HN. It's hyperbole and your explanation ("relatively good approximation for the cancerous like changes [to] workflows") shows as much.
Re:Moving to GitLab by lima on Sunday December 02, 2018 @04:54AM (#18581665)
> Free/open source components of Phabricator feeling half-finished because Phacility has redirected development resources to paid features

There are no closed-source Phabricator components. The email is complaining about development focus being on the wrong parts (the ones paying customers use), rather the ones Haskell uses.