The Fedora Linux release team announced the final stage of the project's migration from its proprietary Pagure platform to a new collaborative development system built on the Forgejo project. At the end of September, Fedora Forge, a collaborative development service based on Forgejo, was launched in test mode for code management and issue reporting. All open and closed issues are scheduled to migrate from Pagure to the new service on November 18, and access to the old bug tracking interface will be disabled.
Thus, after November 18th, all release-related issues 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. The remaining repositories, such as faint and composes, will be migrated next. The reason cited for the platform change is that the Pagure project requires significant maintenance resources, is stagnant, and has not achieved widespread adoption 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 a simple installation process. It provides typical project capabilities, such as task management, issue tracking, pull requests, wiki, tools for coordinating developer groups, preparing releases, automating package placement in repositories, managing access rights, interfacing 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 migrating and mirroring repositories.
Source: opennet.ru
