A development fork of the ForgeFed protocol docs. Official docs live at https://forgefed.peers.community/
|Iko c2d095fccf Adjust bullet and numbered list items||2 years ago|
|doc||2 years ago|
|html||2 years ago|
|rdf||2 years ago|
|spec||2 years ago|
|vocabulary||2 years ago|
|.gitignore||2 years ago|
|COPYING||2 years ago|
|README.md||2 years ago|
|build.sh||2 years ago|
|deploy.sh||2 years ago|
|logo-with-margin.svg||2 years ago|
|logo-with-name.svg||2 years ago|
|logo.svg||2 years ago|
ForgeFed is an upcoming federation protocol extending the W3C's ActivityPub protocol to provide a uniform server-to-server API for interoperability between networked version control services, with limited pub/sub access for messaging and notifications to and from the larger fediverse. It allows users of any ForgeFed-compliant service to interact with other ForgeFed-compliant forge services, without being a registered user of that foreign service, just as if they were. In this way, users that choose to self-host have the additional benefit/responsibility of fully controlling of their own authentication/identityand their own data.
All of the most common user interactions are supported such as: cloning/forking, merge-requests/patches, bug-reports/code-review, subscriptions/favorites with VCS-agnostic, service-agnostic, and client-agnostic genericity.
You can find the latest specification draft at forgefed.peers.community.
The formal work-group and associated development discussions are conducted openly on the ForgeFed Community Forum on the FeNeAs website; with informal, real-time Collaboration often taking place on the #peers IRC channel on freenode. Everyone is invited to participate in either venue. Before posting, please read this primer for a brief overview of the project motivation and goals.
The artifacts produced by this work-group are still in the early stages; and there is still much work to do, and ample design-space for discussion and contributions. In order to be most widely adopted, we strive to assemble the most diverse and representative group of stake-holders including: users, implementers, and various domain experts. Anyone who is experienced with working on an existing forge or a federated "social" service, or who is planning to implement new ones, and anyone with experience in writing technical specification documents, or has UX expertise is encouraged to join the work-group and/or contribute artifacts. Please submit any tangible contributions (artwork, software, documentation) and technical critique regarding the published artifacts to the ForgeFed issue tracker and ForgeFed wiki on NotABug, or the ForgeFed mirror on Pagure.
Connect with ForgeFed on the fediverse for progress updates and general tooting.
All artifacts produced by the ForgeFed work-group are freely available under the CC0 1.0 Universal (CC0 1.0) Public Domain Dedication. All contributions to the wiki must also be offered freely as such.
The ForgeFed logo was contributed by ikomi.