I'd like to continue moving some git projects/repositories from https://git.centos.org to https://gitlab.com/CentOS (and eventually through different under project, like Artwork/Promo/etc). For unknown ones, I'd probably propose to just create corresponding hierarchy and put that under archives, so something like https://gitlab.com/CentOS/archives/git.centos.org/centos/<project_name>. That means we can easily write RewriteRules/Redirect from old to new one if that follows a pattern.

Here is the list of projects hosted under https://git.centos.org/projects/centos/%2A , so I'd like to get opinions about where to move these (and some were probably already "moved" by some SIGs, who probably migrated silently to gitlab.com some time ago) :

* artwork-archive * Artwork * bld-seven * board * buildsys-macros * c6-livemedia * cbs-content-control * cbs-tools * centos-infra-docs * centos-metadata * centos-module-defaults * centos.org * centos-packager * centos-torrents * centpkg * centpkg-minimal * comps * connect * infra-playground * kickstarts * livemedia * pungi-centos * releng * sig-guide * storage-sig-docs * stream-team-docs * t_docker * t_functional

at least I see that can eventually move under Promo SIG (like centos.org website), and some others that some SIGs would like to pick up and host/manage under their SIG umbrella under gitlab.com/CentOS

In lack of reaction to this mail, I intent to just massively import all under archives, *but* also lock these down as archives (so way to to commit/push nor open MR to these)

So if your SIG wants to take ownership of some specific git repositories, that you use in your workflow, now is the time to say so.

PS: Main ticket for git.centos.org is https://gitlab.com/CentOS/infra/tracker/-/work_items/1654 but for different type of projects (like /rpms/* will clearly be a different one), I'll create linked task to main one to reflect status