establish policy on git repository mirroring, hosting and, ultimately migration from gitolite
We have already started mirroring (#18 (closed), #35 (closed)) repositories from gitolite to GitLab. We need to decide how and/or if we will accept such requests in the future, and, in particular, whether we want to host all our git repositories on GitLab in the long term.
If so, we need to come up with a migration plan on how the old repositories on gitolite will "map" to the ones in GitLab. This is particularly complicated by the fact that the namespace established on GitLab does not necessarily reflect the one in use on Gitolite, so we are very likely to have to come up with some rewrite rules to handle those redirections.
But at the very least, we need a plan, and we need it fast, because I am worried this migration will happen organically and we will then have to maintain two git hosting systems in parallel. This is similar to the problem of "hosting both trac and gitlab in parallel" that we have (succesfully, i think) avoided, but it was a near hit. ;)
TL;DR: we need to define the following policies:
- do we keep gitolite around forever?
- if we do, do we keep the old codebase or upgrade?
- if we do not, when do we retire git-rw (cupani) and gitweb (vineale)?
- if we do not, how do we protect our code against the larger attack surface of GitLab?
- where do people create new git repositories? gitolite or gitlab?
- can people mirror their git repositories from gitolite to gitlab?
- how do we mirror a repo from gitolite to gitlab?
- can people migrate their git repositories from gitolite to gitlab?
- how do we migrate a repo from gitolite to gitlab?
- how do we redirect users from gitolite to gitlab?