ForgeFed and federated code forges: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
'''ForgeFed and federated code forges''' describe a way for separate code hosting sites to work together, so that a person registered on one forge can open an issue, star a project or submit a merge request on another without creating an account there. ForgeFed is the protocol that defines those exchanges, and Forgejo, the software behind the nonprofit Codeberg, is the best known forge working to implement it.<ref name="ffhome" /><ref name="codeberg" /> Federation spreads the social layer of software development across many independent servers, which makes it a real but partial answer to dependence on a single platform. | '''ForgeFed and federated code forges''' describe a way for separate code hosting sites to work together, so that a person registered on one forge can open an issue, star a project or submit a merge request on another without creating an account there. ForgeFed is the protocol that defines those exchanges, and Forgejo, the software behind the nonprofit Codeberg, is the best known forge working to implement it.<ref name="ffhome" /><ref name="codeberg" /> Federation spreads the social layer of software development across many independent servers, which makes it a real but partial answer to dependence on a single platform. | ||
__NOTOC__ | __NOTOC__ | ||
== Why federation matters for code == | == Why federation matters for code == | ||
On 23 October 2020 the Recording Industry Association of America sent GitHub a takedown notice under the Digital Millennium Copyright Act targeting youtube-dl, a popular video download tool, and GitHub disabled the repository.<ref name="riaa" /> GitHub reinstated it on 16 November 2020 after receiving new information, and among its policy changes it promised that owners of disabled repositories would be able to export their issues and pull requests where legally possible.<ref name="ghblog" /> | On 23 October 2020 the Recording Industry Association of America sent GitHub a takedown notice under the Digital Millennium Copyright Act targeting youtube-dl, a popular video download tool, and GitHub disabled the repository.<ref name="riaa" /> GitHub reinstated it on 16 November 2020 after receiving new information, and among its policy changes it promised that owners of disabled repositories would be able to export their issues and pull requests where legally possible.<ref name="ghblog" /> | ||
Revision as of 05:36, 16 November 2026
ForgeFed and federated code forges describe a way for separate code hosting sites to work together, so that a person registered on one forge can open an issue, star a project or submit a merge request on another without creating an account there. ForgeFed is the protocol that defines those exchanges, and Forgejo, the software behind the nonprofit Codeberg, is the best known forge working to implement it.[1][2] Federation spreads the social layer of software development across many independent servers, which makes it a real but partial answer to dependence on a single platform.
Why federation matters for code
On 23 October 2020 the Recording Industry Association of America sent GitHub a takedown notice under the Digital Millennium Copyright Act targeting youtube-dl, a popular video download tool, and GitHub disabled the repository.[3] GitHub reinstated it on 16 November 2020 after receiving new information, and among its policy changes it promised that owners of disabled repositories would be able to export their issues and pull requests where legally possible.[4] That promise points to a structural fact. Git is distributed, so every clone of youtube-dl still held the full code history. The issues, reviews and discussion around that code, however, lived only on the platform. Codeberg makes a similar argument in its mission statement: millions of volunteers produce free software that ends up hosted on closed commercial platforms, and it cites the fate of SourceForge as a warning.[2]
How ForgeFed works
ForgeFed is an extension of ActivityPub, the protocol that the World Wide Web Consortium published as a Recommendation on 23 January 2018 and that underlies the fediverse.[5] In ActivityPub every actor has an inbox for receiving messages and an outbox for sending them. ForgeFed extends that idea so that repositories and issue trackers have inboxes too. The project compares it to email, except that the messages are structured JSON objects instead of free text.[1]
The specification sorts objects into activities, actors, child objects and global helpers. Actors such as repositories host their child objects, such as tickets, on their own server. To open an issue on a remote project, a contributor sends an Offer activity containing a Ticket to the project's tracker, and the tracker decides whether to accept it and assign it an address.[6] The specification also defines following, starring, remote pushes, forks and migrations, and the full life of issues and merge requests, from opening and assigning to applying patches and reviewing them.[6]
Vervis is the reference implementation, used as a demonstration platform for testing the protocol. The ForgeFed site lists Forgejo as implementing federation and notes that a ForgeFed plugin for the Pagure forge is unmaintained.[1]
Where Forgejo stands
Codeberg e.V. is a registered nonprofit association in Berlin whose members elect its board. Its site runs Forgejo, a hard fork of Gitea that Codeberg has backed as an umbrella organization since 2022.[2]
Forgejo's first federated feature, the federated star, was merged on 6 June 2024. When a mirror declares that it follows its origin repository, stars given on the mirror are passed along to the origin.[7] The project's federation roadmap marks the star as done; lists unstarring, following user activity and repository search as work in progress; and places federated comments, discussions and pull requests further out.[8]
Federation is disabled by default. In September 2026 a security report described how Forgejo's inbox handlers accepted the actor named in a message body without checking that it matched the key that signed the request, which allowed forged stars and follows on instances with federation turned on. In the discussion that followed, stricter signature checks were proposed as a mitigation.[9]
What federation does not solve
Federation moves messages between servers, but it does not replicate or preserve them. Under ForgeFed an actor hosts its own child objects, so a project's issues still live on its home instance.[6] If that instance shuts down without a mirror, its history goes with it, and every instance remains a server that someone must fund and maintain.
Discovery is also limited. Forgejo's roadmap says plainly that federated repository search makes no claim to completeness and can only find repositories that are somehow connected to the instance doing the search.[8] Trust is harder too, since each server must judge activity sent by strangers, as the 2026 security report showed.[9]
Other projects take a different path. Radicle is a peer-to-peer forge in which repositories are replicated across peers, and issues, discussions and patches are stored as signed Git objects instead of being hosted by one server.[10] Pairing federation with a permanent archive is another option, explored in Permanent wiki and Git forges on AO.
Practical steps today
Projects that want less platform risk can act now. They can host on Codeberg or another Forgejo instance, keep mirrors on more than one forge, export issues on a schedule, and keep federation for test instances until it matures. Developers interested in the protocol can read the ForgeFed specification and try Vervis, and the Forgejo federation repository publishes its architecture and threat analysis openly for review.
Discussion questions, essay ideas, and learning related AI prompt ideas
- Why did the youtube-dl code survive its takedown more easily than its issues and discussions?
- How does modeling a repository as an actor with an inbox change what a code forge can do?
- What are the trade-offs between federation, where each server hosts its own data, and peer-to-peer replication, where many peers hold copies?
- How should a forge decide whether to trust activity sent from an unknown server?
- Why might a federated star be a sensible first feature, and what does it reveal about building federation in small steps?
- What would a fair moderation policy look like for issues opened from other instances?
- Design a backup routine that would let a small open source project survive the loss of its forge.
- How could federated forges and a permanent storage network divide the work of live collaboration and long-term preservation?
Readings from Wikipedia
- ActivityPub
- Fediverse
- Federation (information technology)
- Forgejo
- Codeberg
- Gitea
- Forge (software)
- Git
- Distributed version control
- Fork (software development)
- Youtube-dl
- Censorship of GitHub
See also
External links
- ForgeFed project site
- ForgeFed specification
- Forgejo federation architecture and roadmap
- ActivityPub W3C Recommendation
- Search this wiki for ForgeFed
- Search this wiki for federation
- Search this wiki for Git forge
References
- ↑ 1.0 1.1 1.2 "ForgeFed". ForgeFed project. https://forgefed.org/.
- ↑ 2.0 2.1 2.2 "What is Codeberg?". Codeberg Documentation. https://docs.codeberg.org/getting-started/what-is-codeberg/.
- ↑ "2020-10-23-RIAA (DMCA notice)". GitHub DMCA repository. 23 October 2020. https://github.com/github/dmca/blob/master/2020/10/2020-10-23-RIAA.md.
- ↑ Vollmer, Abby (16 November 2020). "Standing up for developers: youtube-dl is back". The GitHub Blog. https://github.blog/news-insights/policy-news-and-insights/standing-up-for-developers-youtube-dl-is-back/.
- ↑ "ActivityPub, W3C Recommendation 23 January 2018". World Wide Web Consortium. https://www.w3.org/TR/activitypub/.
- ↑ 6.0 6.1 6.2 "ForgeFed specification (branch snapshot, 18 June 2025)". ForgeFed project. https://forgefed.org/spec/.
- ↑ "federated-star, pull request 1680". Forgejo on Codeberg. 6 June 2024. https://codeberg.org/forgejo/forgejo/pulls/1680.
- ↑ 8.0 8.1 "Roadmap for Federation". Forgejo contributors. https://codeberg.org/forgejo-contrib/federation/src/branch/main/FederationRoadmap.md.
- ↑ 9.0 9.1 "Experimental Security Issue: federation activity spoofing via unbound HTTP signature, issue 14271". Forgejo on Codeberg. 7 September 2026. https://codeberg.org/forgejo/forgejo/issues/14271.
- ↑ "Radicle: the sovereign forge". Radicle. https://radicle.xyz/.