On 5/8/26 02:01 PM, Maxwell G wrote:
Hi,
pagure.io is expected to be shut down next month, but it seems there are some
important steps missing. I understand that the Forge team is putting in a lot
work to get the migration completed and that this is no small task. I am just
questioning the deadlines and pagure.io shutdown plan which do not seem
realistic to me.
1. Private issues are not yet supported on the new forge. I am aware that CLE
is currently working on implementing this feature and collaborating with
Forgejo upstream (which is great!), but the feature is not implemented yet and
is not expected to be completed until Q4 2026.
2. The CI situation is still not resolved. It seems Forgejo Actions are
currently available on a by-request basis, but resources are limited and only
unprivileged containers are available which is not suitable for projects that
currently rely on Zuul + Testing Farm to run tests in VMs. I was under the
impression that Packit + Testing Farm was supposed to be the replacement for
Zuul here but was told by the Packit team that implementing support for Forgejo
and Fedora Forge is not a current priority.
3. Important projects have not migrated to Forge, including repos that are
needed to compose Fedora and build images. Some projects can likely be migrated
now, but others are blocked on the aforementioned issues.
Aside: For other projects, we do have the packaging organization available now
[1] to host packaging tooling that did not have a place on Fedora forge
previously. Any member of the packager group can create or migrate repositories
to that organization, but please read the description at [1] and make sure your
repository is in scope for the packaging org before proceeding.
So I'm asking here if some clarity can be provided on items 1 and 2. I
understand that there is a desire to encourage migration to the new Forge, but
I worry having a migration deadline that is not in line with the expected
completion of features and does not account for whether important projects have
actually been migrated is problematic and creates confusion for Fedora
contributors.
Best,
Maxwell
[1]: https://forge.fedoraproject.org/packaging/
I've wondered about this myself. When I was looking for the kiwi files I found
them on https://pagure.io/fedora-kiwi-descriptions although I suppose they may
have already moved to Forgejo since the last time I looked for them.
Steve
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
