Towards federated git collaboration
Git was designed as a decentralized version control system from the ground up. Yet it has been subverted by centralizing hosting and collaboration platforms that compete on projects hosting their code on them. Disagreements on where a project should be hosted regularly result in flame wars. But why, since we live in a world of federated services? If the Git hosters would federate, it might not matter on which server a merge request or an issue is filed.
The #gitea issue targeted at adding #activitypub is still open, but it seems to require in-depth architectural changes. So what would be the best bet for a Git hosting platform to be the first in entering the #fediverse?
The #gitea issue targeted at adding #activitypub is still open, but it seems to require in-depth architectural changes. So what would be the best bet for a Git hosting platform to be the first in entering the #fediverse?
Design Discussion: ActivityPub support + ForgeFed vocabulary · Issue #14186 · go-gitea/gitea
#1612 discusses Federation in general but I wanted to open an issue for the ActivityPub + ForgeFed solution specifically and concretize this unit of work. Let's keep to discussing ActivityPub+F...GitHub
like this
singpolyma doesn't like this.
smallcircles
in reply to dreiwert • • •Forgejo – Beyond coding. We forge.
forgejo.orglike this
poVoq, dreiwert, nachtigall and drop like this.
dreiwert
in reply to smallcircles • • •smallcircles likes this.