The CLE (Community Linux Engineering Team), established at Red Hat to tackle technical challenges for Fedora and CentOS projects, such as providing infrastructure, preparing releases, and ensuring quality, has announced the readiness for usage of the Fedora Forge collaborative development platform, built on the Forgejo project. The Fedora Forge project is created to replace the in-house Pagure platform used in Fedora for collaborative work with code and package metadata. The decision has been made to move away from Pagure, as this platform requires significant resources for maintenance, is in a state of stagnation, and has not gained widespread use outside of Fedora.
Teams participating in the development of Fedora Linux have until June 2026 to transition from pagure.io to Fedora Forge. After the Flock 2026 conference, which will take place from June 14-16, the content of pagure.io will be switched to an archival mode, allowing only read access. Following this, all other services using Pagure, including the source code repositories at src.fedoraproject.org, are planned to be phased out before the release of Fedora 46 in 2027.
Work related to the following will be carried out in Fedora Forge:
- maintaining the project's infrastructure (configuration management, development of deployment tools and scripts);
- preparing releases and maintaining packages (tools, utilities, and templates for building, generating, and distributing Fedora releases);
- organizing project workflows (preparing documentation and specifications, collaborative work among teams);
- Development of Fedora-specific applications, such as Fedora Badges, Bodhi, and fedmsg.
Personal projects directly unrelated to Fedora are prohibited from being developed in Fedora Forge. Fedora Forge should also not be used as a primary platform for developing third-party projects, even if packages for them are distributed in Fedora repositories.
It is noted that not all functionalities of Pagure have been implemented in Forgejo yet. For instance, there are no necessary tools for conducting confidential discussions in public repositories (private issues for discussing vulnerability fixes before information disclosure). Currently, Fedora representatives are working with the Forgejo developers on implementing the missing features.
The Forgejo platform is a fork of the Gitea project, which in turn branched off from the Gogs platform. Key features of Forgejo include low resource consumption (can be used on inexpensive servers... VPS) and a simple installation process. Standard project management capabilities are provided, such as task management, issue tracking, pull requests, wikis, tools for coordinating groups of developers, release preparation, package deployment automation in repositories, access rights management, integration with continuous integration platforms, code search, authentication through LDAP and OAuth, repository access via SSH and HTTP/HTTPS protocols, connecting webhooks for integration with Slack, Discord, and other services, support for Git hooks and Git LFS, and tools for repository migration and mirroring.
Source: opennet.ru
