Fedora Forces Abandonment of Pagure.io: Forgejo's GPL Licensing Sparks Technical Ire Among Developers
Fedora mandates a full infrastructure migration from pagure.io to Fedora Forge, which utilizes Forgejo. This shift is set for completion by the Fedora 46 release in 2027, when all existing Pagure package source repositories on src.fedoraproject.org retire.
Discussion centers on the technical details of this forced transition and Forgejo's new copyleft licensing structure. While the CLE team strongly pushes adoption of Fedora Forge, user 'tabular' flagged the licensing choice, questioning the shift to GPL over AGPL for a collaboration service. Furthermore, the name 'Forgejo' itself has spawned light mockery, with users pointing out its awkward phonetic pronunciation.
The weight of the discussion points to an unavoidable infrastructure overhaul. The community accepts the target timeline for Pagure's end but remains divided over the ideological ground being established by the new GPL license backing the core collaboration tools.
Key Points
Mandatory replacement of pagure.io with Fedora Forge/Forgejo.
The CLE team asserts this is the designated, modern platform for Fedora Infrastructure.
Hard deadline set for Pagure.io's complete retirement.
The transition is phased, culminating in the retirement of all Pagure instances by Fedora 46 in 2027.
The adoption of Forgejo's GPL licensing is controversial.
User 'tabular' specifically questioned the choice of GPL over AGPL for a collaboration service.
General preparation for the new ecosystem is required.
The CLE team urges immediate familiarity with Fedora Forge to prep teams for the ecosystem shift.
The technical licensing update on Forgejo itself.
A 'Forgejo Update' confirmed the licensing structure has moved toward copyleft.
The name 'Forgejo' is phonetically difficult.
User 'auroz' noted the name's awkward pronunciation, leading to varied phonetic attempts.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.