I am considering a Community Blog post (and a Discussions post naturally comes along with it) and an email to the Fedora Devel list with the link to the Community Blog post so that people begin self-enrolling themselves in the migration. As this is Pagure.io migration, we need not worry about having to migrate every one of the repositories there because I do not suppose that we plan to open our new Forgejo deployment to the general public, do we?

The reduction in our capacity to host other repositories or mirrors that are not related strictly to Fedora Project is a sensitive affair. The messaging around it must be conveyed correctly as the last thing we need is more backlash. As these are Pagure.io repositories, it would be a wiser decision to ask folks (the repositories and organizations of whom we plan on having) to self-migrate using Pagure Exporter when the Forgejo support is done.

No, the new forge will not be opened to the general public. We will host only projects directly related to the Fedora Project. We will encourage general projects that are hosted on pagure.io to move to codeberg.org

From pagure we will for sure be migrating all the fedora bodies. Council, Fesco, Mindshare, SiGs,...

One of the aims of this effort is to unify our forges. So we will migrate the Fedora namespace on gitlab.com, github.

Moved to https://codeberg.org/fedora/forgejo-deployment/issues/21