Federated Code Hosting https://wrt.nth.io/luke/federated-code-hosting
@Luke @luke @codeberg Yeah it's exactly what everyone wants, except the big vendors like github and GitLab. #Gitea and sr.ht are probably the only parties actually interested and they don't have the resources to make it happen. Even though the recent news (2 months ago?) that there was going to be a person fully dedicated to it, is very promising!
I can't find the reference, it's somewhere in one of my toots.
That's how git development started in the good'ol days ;)
You surely refer to https://drewdevault.com/2018/07/23/Git-is-already-distributed.html ? Metadata, issues, PRs, wiki are an issue tho
@codeberg @clacke @Luke Git might be, but the vast majority of repositories where all our projects reside are not. They are centralized, require logins in order to file an issue or submit a patch/merge request.
Also I don't know how Git-native patches are. Do patches with multiple commits exist, f.e.? Can they contain signed commits that go into the master branch signed?
A distributed "merge request" protocol seems different than sending patch files over email.
> Can they contain signed commits that go into the master branch signed?
Signing is offloaded to email protocol, iirc
> A distributed "merge request" protocol seems different than sending patch files over email.
We agree: this was not our proposal, we just wanted to link to the historical reference for context ...
We surely do not agree with every link cited
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!