Migrating Repositories to Forgejo

Project Discussion
, ,
1

Hey everyone,

As you may know, we’re making progress on the exciting move of Fedora-related repositories and organizations from Pagure.io to Forgejo!

I’ve started a preliminary list of organizations and repositories that we believe will be migrating over to Forgejo on the wiki page here: Organization Layout - fedora/forgejo-deployment - Codeberg.org.

Now, we need your help to make this list as comprehensive as possible. If you know of any other Fedora-related repositories or organizations that are planning to move to our new Forgejo instance, please take a moment to add them to the wiki page.

Important Note: We are only migrating repositories that fall under a Fedora group or Special Interest Group (SIG). Any repositories that don’t belong to a Fedora entity will need to find a new home elsewhere, such as Codeberg, GitLab, or GitHub. Please keep this in mind as you contribute to the list.

Cheers,
ryanlerch

8 Likes
2

You have the Docs repo from Join SIG, but there are two more under Join SIG

3

Fedora Personal Systems WG: Overview - fedora-personalsystems/wg - Pagure.io

Fedora KDE has many more repos.

1 Like
4

There are a number of CentOS organizations that should move to the new forge too. For example, the CentOS Hyperscale SIG and CentOS Alternative Images SIG are there.

5

Why would CentOS repos not use the CentOS project on GitLab to be with the rest of the CentOS stuff, rather than Fedora…?

Conversely: currently some Fedora projects are using GitLab, which is extremely confusing. We should put Fedora stuff on Forgejo to keep things in one place.

6

We will likely want most (or all) of the projects under the fedora-rust namespace to move too:

https://pagure.io/projects/fedora-rust/*

Note that the namespace doesn’t need to be the same - if this will live under a fedoraproject.org domain, it could just be a rust-sig namespace.

7

Go SIG

Packager tools

I have the following packager tools that I’d like to move to a namespace for packager tools

8

That’s the plan, but it requires time and effort

9

Can you migrate the repos of the i3 SIG?

10

These predate GitLab being available for CentOS SIGs. I do agree that in most cases it makes more sense for SIGs to use GitLab here, and that’s likely what we’ll be encouraging on the CentOS side. That said, I don’t think we need a hard policy on this.

11

I have Overview - find-inactive-packagers - Pagure.io (and the “testing” repo find-inactive-packagers-test) that I think should be moved under the infra namespace.
But I’ll need to adjust the script to work with Forgejo.

12

Would the Fedora Podcast repo fall under any specific SIG? (probably marketing?)

I’m good with keeping it on GItlab if we are still going to keep that around, I just wasn’t sure on all the details there.

13

The Cloud SIG has a couple, the two I’m aware of are:

14

Flatpaks SIG:

ELN SIG:

1 Like
15

Adding here as I can’t edit the wiki:

Fedora Atomic Desktops SIG:

1 Like
16

The Asahi SIG has repos under https://pagure.io/projects/fedora-asahi/%2A. Most of these are hooked up to copr and will require coordination (and possibly work on the copr side). fedora-asahi/kiwi-descriptions is hooked up to our build pipeline and will also require coordination.

17

The Fedora Btrfs SIG at https://pagure.io/projects/fedora-btrfs/%2A needs to be migrated.