Migrate repositories from git.a.o to GitLab
Now that we have integrated GitLab into Alpine infrastructure it's time to looks at migrating git.a.o repositories to GitLab projects. This is probably also a good time to cleanup git.a.o and remove some older and obsolete repositories.
Looking at the current list on git.a.o we have:
Alpine Projects
, Docs
, ACF
, Hosted
, user
- Docs and ACF are already migrated to GitLab.
- Hosted has not been migrated at all, so we need to check what to do with those repositories.
- Users have probably already started to shift their repos to GitLab, we need to double check this.
To keep complexity and maintenance burden low, I would suggest to only mirror the most important repositories to git.a.o. This can be done automatically via the repositories settings in the project and push on update. The two major reasons to keep repositories and mirror them on git.a.o are:
- Do not break customer remotes
- Provide an alternative self hosted mirror (we also keep our github mirrors)
For mirroring I would suggest to skip ACF, Docs, Hosted and user and only mirror a selection of Alpine Projects:
-
abuild -
alpine-baselayout -
alpine-conf -
alpine-mksite -
apk-tools -
aports -
mkinitfs -
alpine-secdb
From this list I would like to address aports
specifically as this is the main alpine repository and probably needs some special attention. Not sure we should make this a separate issue.
- Path based ACL: alpine/infra/docker/gitlab@be19b641
- Add all developers with commit access to aports project