Matthew Miller, a project leader of Fedora, introduced an initiative to move away from using its own collaborative development platform, Pagure. As a replacement, the Fedora Council preferred the Forgejo platform, but before confirming the transition to Forgejo, it decided to conduct a public discussion of its choice and consider the community's opinion. The final vote will take place in two weeks, and until then, anyone can share their thoughts regarding the decision made.
The current proprietary platform, Pagure, has become outdated, requires substantial resources for maintenance, is stagnating, and has not gained wide adoption outside of Fedora. In 2020, an attempt was made to replace Pagure with GitLab, but this initiative did not advance beyond discussions. This year, after evaluating existing collaborative development platforms, it was concluded that the project needs an open solution suitable for deployment on its own servers. The GitLab Community Edition and Forgejo best met the established criteria.
Both GitLab and Forgejo platforms have their pros and cons, and both require certain enhancements to recreate the functionality of the Dist Git platform based on Pagure used in the development of Fedora Linux. In particular, the new platform will need to ensure integration with related project services such as Bodhi, Fedora CI, COPR, Fedpkg, Hotness, Fedora Notifications, Toddlers, Fedora Messaging, Monitor Gating, Release Engineering Scripts, Fedora Packagers, and Packit.
Weighing all the arguments, the members of the governing council chose Forgejo as the preferred platform because it is developed by an independent community, while GitLab is a product of a commercial company developed under an Open Core model, where some advanced features, including those needed in Fedora, are only available in the commercial product. Concerns were also taken into account that GitLab's policy might change over time, making the project less open. An additional argument in favor of Forgejo was that the Go language and Forgejo's codebase were more familiar to the team responsible for infrastructure in Fedora than Ruby, which is used in GitLab.
A Forgejo platform is designed for deploying a collaborative system with Git repositories, similar to the tasks solved by GitHub, Bitbucket, and Gitlab. Forgejo is a fork of the Gitea project, which in turn branched off from the Gogs platform. The separation of Forgejo occurred in 2022 after attempts to commercialize Gitea and the management being handed over to a commercial company. Within the Forgejo project, independent developers aimed to maintain the previous principles of independent governance and community oversight. The project's code is written in Go. Starting from release 9.0, Forgejo code is distributed under the GPLv3+ license, while the old code remains under the MIT license.
The key features of the Forgejo platform include low resource consumption (it can be used on a Raspberry Pi or inexpensive hardware). VPS) és az egyszerű telepítési folyamat. Alapvető projektkezelési funkciók állnak rendelkezésre, például feladatkezelés, probléma-nyomkövetés (issues), pull-kérések, wiki, fejlesztői csoportok koordinálására szolgáló eszközök, kiadások előkészítése, csomagok tárolókba történő automatikus kihelyezése, hozzáférési jogok kezelése, folyamatos integrációs platformokkal való összekapcsolás, kódkeresés, LDAP és OAuth általi hitelesítés, tárolók elérése SSH és HTTP/HTTPS protokollokon keresztül, web-hookok csatlakoztatása Slack, Discord és más szolgáltatások integrálására, Git-hookok és Git LFS támogatása, valamint eszközök tárolók migrálására és tükrözésére. Külön kiemelhető az ActivityPub protokoll használatának lehetősége, amely lehetővé teszi az egyes szerverek fejlesztőknek szólnak.
Forrás: opennet.ru
