Re: [RFC] switch to GitLab / gitlab.com

[David Kastrup]

Jonas Hahnfeld <address@hidden> writes:

[Not repeating well-thought considerations]

> Closing thoughts
> ================
>
> GitLab has a feature called 'Repository mirroring' [8], working in both
> directions. During the switching period, we could maintain Savannah as
> our main repository and let GitLab pull in changes from there. After a
> final cut, GitLab could instead be configured to push master and
> stable/* branches to Savannah.

It's worth stating that the large migration hurdle is actually saving as
much from tracker/review setup we have as possible.  Switching Git
repositories, in comparison, is a rather small hurdle.  We need to get
our ducks in a row regard the contributor documentation and scripts, but
otherwise that part is rather simple (famous last words).

> Links
> =====
> 1: https://git.savannah.gnu.org/cgit/lilypond.git/
> 2: https://sourceforge.net/p/testlilyissues/issues/
> 3: https://codereview.appspot.com/
> 4: https://gitlab.com/explore
> 5: https://www.gnu.org/software/repo-criteria-evaluation.html
> 6: https://www.gnu.org/software/repo-criteria.html
> 7: https://docs.gitlab.com/ee/user/project/settings/import_export.html
> 8: 
> https://docs.gitlab.com/ee/user/project/repository/repository_mirroring.html
>

-- 
David Kastrup