The team responsible for preparing Fedora releases Linux, 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, the Fedora Forge collaborative development service, powered by Forgejo, was launched in test mode for code management and issue resolution. On November 18, all open and closed issues are scheduled to be migrated from Pagure to the new service, and access to the old issue 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. Forgejo's key features include low resource consumption (suitable for low-cost VPS) and a simple installation process. Standard project management features are provided, such as task management, issue tracking, pull requests, a wiki, tools for coordinating development teams, release preparation, automated package deployment to repositories, access rights management, integration with continuous integration platforms, code search, LDAP and OAuth authentication, repository access via SSH and HTTP/HTTPS, webhooks for integration with Slack, Discord, and other services, support for Git hooks and Git LFS, and tools for migrating and mirroring repositories.
Source: opennet.ru
