GNOME Migration to GitLab
Background
GNOME has been considering migrating to GitLab over the past months. I have been in touch with the community to follow and assist them in the decision to migrate.
Discussion
The GNOME community has identified certain blockers in their migration. We've committed to addressing those blockers for the community to make the migration possible. To guarantee the migration we've stated that rebase will only get merged after we receive word from GNOME about their final decision regarding the migration.
Migration Order of Events
I had a discussion (privately shared) with @csoriano on the topic of the final decision and that has been reached. To guarantee a safe move of rebase to CE and the migration of GNOME projects to GitLab we've agreed to follow the flow detailed hereafter, chronologically ordered:
-
GitLab will assign the rebase blocker to a release -
The GNOME (community) engagement team will move to GitLab by end of November 2017 -
6 GNOME projects will move to GitLab by end of November 2017 -
14 GNOME projects, for a total of 20, will move one release before the rebase blocker will be merged. -
Once rebase blocker is closed & merged, the GNOME Software core project will migrate within the one month. The GNOME Shell and Mutter core projects will migrate within two months. -
Once the above has been completed and migrated, GNOME will make a public announcement about the migration and change of workflow (blog post and PR). GitLab will optionally do: a PR, blog post and video interviews with GNOME members discussing the analysis and decision process . All content will be in sync with GNOME community leaders to ensure proper wording due to the sensitivity of the move within the GNOME community. - Gtk and GLib core projects will take longer to migrate as they are the heaviest in terms of activity volume and possible legacy complications.
Collaborators
- @eliran.mesika from GitLab
- @csoriano, @aruiz from GNOME