@rabble have you looked into GitWorkshop?
#ForgeFederation
Ever since BorgSoft bought #GritHub, I've been maintaining a list of community-hosted code forges here;
https://wiki.p2pfoundation.net/List_of_Community-Hosted_Code_Forge_Instances
My goals for it are to;
* demonstrate that there are replacements for GH that don't require projects to host their own
* showcase the range of independently-hostable code forge software available
* to maintain a list of forges that might be keen to try a federation plugin, if and when there's working code available
(1/2)
It seems like @forgefed's grant funding ran out and the entire project has just been left hanging, unfinished. This is a potentially important project, so this is really frustrating.
But really, anything important enough to get grant funding probably ought to keep going after the grant funding ends. Maybe grant-making orgs could provide some kind of support for projects transitioning out of funded work sprints, back into volunteer-driven coordination?
(1/2)
@gvwilson
> what I'm after right now is worked-out plans I can learn from
For what exactly? Choose one or more of;
* Exporting a full org/ repo and all associated data from a forge
* choosing a new forge
* Importing those orgs/ repos into a forge
* Local-first code collaboration using web forges only as dumb syncs (eg Nostr)
* Federating projects across forges, so no one forge is a SPoF
A few approaches have been tried for most of these.
This video of a FOSDEM talk about Forgejo's forge federation work has the slideshow fullscreen, with a camera feed of speaker Michael Jerger inset in the corner;
https://archive.fosdem.org/2025/schedule/event/fosdem-2025-5610-show-and-tell-federation-at-forgejo/
This is the way.
(1/2)
GitLab is dropping plans to pursue federation features like distributed merge requests. Sad, but not very surprising to me.
https://gitlab.com/groups/gitlab-org/-/epics/260#note_2910231358
However, @forgefed and related specifications are still a thing and @forgejo is still working on supporting that, see https://codeberg.org/forgejo-contrib/federation and https://forgefed.org/!
#forgefed #ForgeFederation #gitlab #forgejo #federatedGit #git
@meissa
> It was silent around progress on federation in forgejo
Is there a blog or a fediverse account where I can find periodic updates on forge federation progress? In general, or about Forgejo work in particular, either would be great.
@forgefed can do with some help.
Please refer to my Call to Fediverse, regarding #ForgeFed and #ActivityPub #ForgeFederation status in general.
@smallcircles suggested:
> “Or try @forgejo — the code #forge that #Codeberg is based on.”
I agree completely & in #copyleft-@next project, we're using #forgejo <https://git.copyleft.org/>!
I mentioned @Codeberg specifically upthread (& not other options) b/c (a) 500-char #Mastodon limit & (b) <https://codeberg.org> is likely the best option for those who want to #GiveUpGitHub <https://giveupgithub.org> quickly.
Absolutely, #ForgeFederation is the future: #Fediverse for CODE!
Cc: @forgefed
Or try @forgejo, the code #forge that #Codeberg is based on.
#Forgejo already has some #ActivityPub-based capabilities e.g. to federate stars, testing the waters for more to come. In their contrib community a whole @forgefed #ForgeFederation initiative is brewing..
It's been far too long since I haven't updated this properly, but here's a snapshot of some open source communities that have already moved off GritHub;
https://wiki.p2pfoundation.net/List_of_Community-Hosted_Code_Forge_Instances
It seems like forge federation is a harder problem to crack than we thought when BorgSoft bought GH. But I'm still hopeful that one day, many of these forges will interoperate to create the experience of a unified code forging space.
Thanks for sharing @sarahjamielewis, great to see more work being done on independent code-forging. Have you given any consideration to interoperation with other forges? Eg implementing @forgefed along with @forgejo and others who are working on that. Or using Git's inbuilt features to interop with SourceHut instances.
@lapingvino
> though Codeberg does like to add more functionality to it for practical reasons, most significantly federation, basically making a Git Forge Fediverse
@Codeberg and the Forgejo devs have been enthusiastic supporters of forge federation. But efforts to get it working precede the forking of Gitea to create Forgejo.
I first started hearing about ForgeFed and other federation projects around the time BorgSoft assimilated GritHub.
@drwho
> You could use that as the data storage medium for forge interoperability. If it's in the notes, it can be used
Has this been considered by any of the existing forge federation projects?
It would be great if we could figure out ways for code forges using different decentralisation protocols to interoperate.
For example, enabling an account on CodeBerg, federating over ForgeFed (AP-based), to contribute to a codebase developed using GitWorkshop (Nostr-based), and vice-versa. Or allowing either to interop with accounts and codebases on a SourceHut instance.
Could there be a way to do this with the distributed code forge tools built into Git itself?
#TIL about #GitWorkshop;
"Gitworkshop.dev, git-remote-nostr and ngit are tools to enable code collaboration over nostr. Gitworkshop.dev provides a visual interface to discuss proposals and open issues. git-remote-nostr enables proposal creation, review and incorporation using standard git tooling. ngit handles repository setup and advanced proposal submission."
Here's something interesting for those interested in reduced vendor lock-in in forges: git-bug, a "distributed" bug tracker "fully embedded in Git" that "prevents vendor lock-in" and doesn't "pollute your project" with "bridges to other bug trackers".
@njoseph
> My code is mostly on Debian Salsa and my own Gitweb. Recently started using Codeberg too
Great stuff. The more we ignore the BorgSoft propaganda that HutGub is where the action is and move elsewhere, the less true that propaganda is.
Bring on forge federation!
Something wicked this way comes.
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst