Migrating the GitHub organization 'valueflows' to GitLab, instance lab.allmende.io
Continuing from the discussion in https://github.com/valueflows/valueflows/issues/526, here I am proposing a suitable workflow for migrating user-generated content and users off from GitHub, in this case towards an independent, community-based GitLab instance maintained as a Common at lab.allmende.io. It is provisioned as one of the core contributions of the not-for-profit association Ecobytes to the public domain.
To conduct the migration, we want to make use of the automatic import capabilities of GitLab, and can prepare the environment a little to increase the level of re-integration. Commits and comments will be mapped to an existing GitLab user, if (a) it exists in advance and (b) has the same email identities used in commits and configured in the GitHub profile associated.
-
Create valueflows group https://lab.allmende.io/valueflows -
Add group description
-
-
Onboard existing users - via manual registration on https://lab.allmende.io/
- via email invitations sent from https://lab.allmende.io/groups/valueflows/-/group_members
-
Add users to the Value Flows organisation - via a click to request to join the group on https://lab.allmende.io/valueflows
- via the group members page at https://lab.allmende.io/groups/valueflows/-/group_members
-
Replicate permissions from GitHub -
Import organization and projects ¹ ²
¹ https://lab.allmende.io/help/integration/github.md - in place ² https://lab.allmende.io/help/user/project/import/github.md - workflow
An additional effort comes with keeping visibility of the organisation on GitHub. Here we can make use of the the repository mirroring ³ functionality, that allows to republish pushed commits to a remote target.
-
Configure repository mirroring for all valueflows repositories
³ https://lab.allmende.io/help/user/project/repository/repository_mirroring.html