...
- Create a copy of the code in Gitlab under gitlab.com/anuket-transition
- Develop Gitlab-CI, utilizing shared runners and Lab-as-a-Service hardware where needed, and produce a .gitlab-ci.yml file between the projects current CI and Gitlab.
- Propose the .gitlab-ci.yml file for inclusion into the project (the project signs off on the work and merges, the change is not pushed directly to the repository).
For projects at gerrit.opnfv.org, this will be a patchset.
For projects at github.com/cntt-n, this will be a PR. - Create the project under gitlab.com/anuket and configure permission schemes, and DCO.
- Enroll the hardware in Gitlab, while marking the runner as offline so as to not run any jobs.
- Enroll project committers and contributors in Gitlab.
- Train the project on Gitlab processes and Gitlab-CI.
- Mirror the project under gitlab.com/anuket
For projects at github.com/cntt-n this will be an import, and need to be scheduled (see N ext Next step).
For pilot projects, this will be a move from their current location to the new group. - Schedule a time (communicate to contributors in advance) with the project to cut-over development and hardware (This can be schedule for everyone at once, if desired).
- Update the original repository description with a notice that the project has moved, and mark the project as archived (read-only).
- Remove project jobs from previous CI, remove project from gitlab.com/anuket-transition.
...