Just please make a point of notifying XCP-ng (https://xcp-ng.org) earlier than the general announcement. So they can update their processes to handle this change without breakages, as they’ll be accessing this for patches.
Sent from my iPad
On 17 Apr 2025, at 22:15, Davide Cavalca dcavalca@centosproject.org wrote:
On 2025-04-16 23:52, Fabian Arrotin wrote:
On 16/04/2025 23:29, Amy Marrich via devel wrote: Fabian, I reached out to Steve to contact Legal and there are no issues with moving the archives to GitLab. Thanks, Amy
Perfect ! so I guess that it means gitlab.com/CentOS and not gitlab.com/redhat (in that case they'd need to do the work as we don't have access to that namespace). How does the board want to proceed with the gitlab migration ? SIGs can opt-in to slowly migrate projects there ? Once we'll move/archive git.centos.org/rpms/* to gitlab, no SIG would ever have access to these in the usual sig branches (no regex rule in ACL will be migrated)
Here's my suggestion:
- SIGs can and should start migrating to GitLab now
- we should pick a flag day for when git.centos.org will become read-only, and announcing ahead of time so folks can plan around it
- on the flag day, we stop allowing writes to git.centos.org
- we migrate everything that's currently on git.centos.org to gitlab.com/CentOS/Archive (or something like that); ideally we'd use the pagure exporter tool, but it looks like it doesn't support git.centos.org yet (see https://github.com/fedora-infra/pagure-exporter/pull/172)
- we flip the archive bit on all the repos migrated to gitlab to make it clear they're archives and people shouldn't push to them
- we eventually shut down git.centos.org
This way there should be no loss of data (as everything will be preserved), and SIGs can move things at their leisure as-needed. Does this plan sound reasonable?
Cheers Davide _______________________________________________ devel mailing list -- devel@lists.centos.org To unsubscribe send an email to devel-leave@lists.centos.org