GitHub considered harmful

[Mathieu Bridon]

On Thu, 2019-10-10 at 10:53 +0200, Alexander Larsson wrote:
> On Thu, Oct 10, 2019 at 12:35 AM Michael Gratton <mike at vee.net>
> wrote:
> > Would it be possible to get an idea of what the main technical
> > hurdles for this would be? From my perspective the two big issues
> > are automating the migration of the repos and updating the build
> > infrastructure and integration. Does that sound about right?
> 
> From a pure technical perspective: Migration of repos is trivial with
> git, but migration of issues and history with things like references
> to PRs etc is much more complicated.

Last I imported a Github project into Gitlab, the importer built into
Gitlab correctly imported all the merge requests and issues, with
correct references, in addition to the Git repo.

If contributors have an account in the destination Gitlab and have
linked it to their Github account, then all attribution (issues, merge
requests, …) is preserved as well.

I was impressed by how well it worked, and had to redo it a few times
before I believed it. :)

(but that's only one of the points you mentioned)

> I realize people might not want to use github for this (or whatever
> other personal reason) though, so we should maybe look at alternative
> ways for people to submit code. For example, I already own
> https://gitlab.com/flatpak, and we could easily set up a mirror of
> github there, and then you can branch that and email merge requests.

Could we have a Flathub organization on (for example) gitlab.com **in
addition** to Github, and the Flathub maintainers who wish to maintain
their projects there could do the switch?


-- 
Mathieu