@luke @Luke You heard of , right? IIRC @codeberg sponsored a full-time person to work on that and implement in .

@stevenroose @luke @codeberg haven't heard of it. Exactly what I want! Sr.ht is even listed as a discussion member. Looks like it hasn't had much activity since last year? 😕 Maybe it was too broad scope and ambitious?

@Luke @luke @codeberg Yeah it's exactly what everyone wants, except the big vendors like github and GitLab. 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.

@clacke @Luke @stevenroose @luke every git repo supports federation over email. Look into git-send-email and git-apply-patch.

That's how git development started in the good'ol days ;)

You surely refer to drewdevault.com/2018/07/23/Git ? Metadata, issues, PRs, wiki are an issue tho

Follow

@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.

@stevenroose @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.

indeed!

> Also I don't know how Git-native patches are. Do patches with multiple commits exist, f.e.?

Thats how it works, yes ... see the git-send-email and git-apply man pages for details....

@stevenroose @clacke @Luke

> 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

@stevenroose @Luke @codeberg You are preaching to the choir, I was just explaining why SourceHut supporting ForgeFed was unlikely. The actual work that received funding is ForgeFed for Pagure and Gitea.

@stevenroose in fairness to Drew, SourceHut supports a lot more of this UI than people realize, by making some very creative use of email protocols. In the medium term I'd like to see code forges experimenting with federating over both sr.ht and ForgeFed. That way it's more likely they'll coverge in some way.

#SourceHut #ForgeFed #CodeForge #email #ActivityPub

@codeberg @clacke @Luke

Sign in to participate in the conversation
unidentified instance

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!