[GHC DevOps Group] The future of Phabricator

[Ben Gamari]

"Boespflug, Mathieu" <m at tweag.io> writes:

> Hi Ben,
>
> On Tue, 30 Oct 2018 at 18:47, Ben Gamari <ben at well-typed.com> wrote:

...

>
> The important things are: reducing the maintenance burden (by
> preferring hosted solutions) while still meeting developer
> requirements and supporting a workflow that is familiar to most.
>
Right; I believe that GitLab checks all of these boxes.

>> Ultimately Rust's tools all exist for a reason. Bors works around
>> GitHub's lacking ability to merge-on-CI-pass, Highfive addresses the
>> lack of a flexible code owner notification system, among other things.
>> Both of these are features that we either have already or would like to
>> have.
>
> ... and I assume based on your positive assessment, are both
> out-of-the-box features of Gitlab that meet the requirements?
>
Yes, GitLab has support for both of these features natively.

>> On the whole, I simply see very few advantages to using GitHub over
>> GitLab; the latter simply seems to me to be a generally superior product.
>
> That may well be the case. The main argument for GitHub is taking
> advantage of its network effect. But a big part of that is not having
> to manage a new set of credentials elsewhere, as well as remembering
> different user names for the same collaborators on different
> platforms. You're saying I can use my GitHub credentials to
> authenticate on Gitlab. So in the end we possibly wouldn't be losing
> much of that network effect.
>
Precisely, GitLab supports OAuth authentication, so one can login with
GitHub credentials.

Cheers,

- Ben

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20181101/6a74b54e/attachment.sig>