FedoraReview

#539 Move upstream to a different forge
Opened by frostyx. Modified

Open
Close Issue

I'd like to start a discussion about moving the fedora-review upstream to a different forge.

Why?

  • Pagure is dead, and we will have to move eventually
  • I want to set up CI for PRs and main branch
  • I want to simplify the release process

Of course everything could be done on Pagure, but it would be a waste of time since we will need to migrate in the future anyway.

Where?

IMHO, the only choices that make sense are:

  • https://github.com
  • https://forge.fedoraproject.org

I am not sure under which organisation the project should live though.

How

It depends on where we are going to migrate.

  • If GitHub, the Copr team migrated several projects and their issue and PR history from Pagure to GitHub. We could use the same migration script
  • If Forgejo, we can use this https://docs.fedoraproject.org/en-US/forge-documentation/migration/pagure_repository/

I am volunteering to do the work.

Vote

We have 7 maintainers of this project and I think it is fair if we collectively vote what we want. Please vote -1 if you want to stay on Pagure, or +1 and let us know your preferred Forge and organisation.

Not sure if I should be the first one or the last one to vote since I am the one proposing this.

But for me, it is +1, and I'd move it to https://github.com/fedora-infra

I'd prefer this under forge.fedoraproject.org

I'd prefer this under forge.fedoraproject.org

The latest information I have is that this forgejo instance will not have capabilities to run CI workflows beyond simple stuff like "deploy a web page" unless you want to connect your own self-hosted Forgejo Actions runners. This is why I moved some Rust SIG projects to codeberg.org instead (where we now have working CI pipelines!).

Based on the information I have right now, I would vote for moving to codeberg.org or to forge.fp.o iff the default Actions runners available there end up being useful enough for this project's needs after all.

I'd prefer for us to be on a Forgejo deployment, if for nothing else because the end state will eventually be forge.fedoraproject.org anyway.

The latest information I have is that this forgejo instance will not have capabilities to run CI workflows beyond simple stuff like "deploy a web page" unless you want to connect your own self-hosted Forgejo Actions runners

Depends on what falls under "simple stuff" but this sounds like this could be a big limitation. Do you know where I could read more about this, please?

No, sorry. This was just information I got when asking about the Forge migration during meetings on Matrix. I suggest taking this question to the Forgejo deployment room - the situation might have changed since I asked last.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.