The team responsible for preparing Fedora Linux releases announced the final stage of migration of the project from its own platform Pagure to a new collaborative development system, built on the basis of the Forgejo project.
At the end of September, the collaborative development service Fedora Forge was launched in test mode based on Forgejo to work with code and parse problem messages (issues). On November 18, all open and closed issue messages will be transferred from Pagure to the new service, and access to the old bug tracking interface will be disabled.
Thus, after November 18, all issues related to releases and their preparation will be available for publication only through Forgejo. The migration will also affect the main RelEng repository, which was previously mirrored in Forgejo. Next, the remaining repositories will be transferred, such as faint and compositions. The reason cited for the platform change is that the Pagure project requires large resources to maintain, is stagnant, and is not widely used outside of Fedora.
The Forgejo platform is a fork of the Gitea project, which in turn forked from the Gogs platform. The key features of Forgejo are low resource consumption (can be used in cheap VPS) and simple installation process. Typical project management capabilities are provided, such as task management, issue tracking, pull requests, wikis, tools for coordinating development teams, preparing releases, automating the placement of packages in repositories, managing access rights, pairing with continuous integration platforms, code search, authentication via LDAP and OAuth, access to the repository via SSH and HTTP/HTTPS protocols, connecting web hooks for integration with Slack, Discord and other services, support for Git hooks and Git LFS, tools for migration and mirroring of repositories.