[petsc-dev] moving from BitBucket to GitLab

[Jed Brown]

Alexander Lindsay <alexlindsay239 at gmail.com> writes:

> I'm assuming this would be served out of an Argonne domain?

No, gitlab.com.

> On Sun, Jun 16, 2019 at 12:49 PM Jed Brown via petsc-dev <
> petsc-dev at mcs.anl.gov> wrote:
>
>> "Zhang, Hong via petsc-dev" <petsc-dev at mcs.anl.gov> writes:
>>
>> > If it is mainly because of CI, why don't we host petsc on GitHub and use
>> the GitLab CI?
>> > https://about.gitlab.com/solutions/github/
>>
>> There are significant missing features for that mode of operation.
>>
>> https://gitlab.com/gitlab-org/gitlab-ce/issues/60158
>>
>> > GitHub has been the biggest social network for developers. Changing a
>> utility is easy to me, but changing a social network isn't.
>>
>> From a previous conversation with Barry:
>>
>> | Barry writes:
>> | >   BTW: You're going to get some abuse for advocating for GitLab and
>> not GitHub; I don't care because I'm a contrarian but it would be good if
>> you had a few sentences about why moving to GitLab is
>> | > better than GitHub (and it can't be open source philosophy arguments
>> :-)
>> |
>> | The short answer is that I think the PR integration with CI/metrics is
>> | clearly superior to anything presently available at GitHub, GitLab can
>> | import all the issues/pull requests/comments, and GitLab supports math
>> | in comments.
>> |
>> | GitHub has more community visibility.  If everyone wants to move there,
>> | it'd be okay with me, but wouldn't completely resolve the CI situation
>> | and we'd lose lots of our history.  On purely technical merits outside
>> | of CI and import, I think GitLab is on par with GitHub.
>>