Running all our own forgejo instance is well and good but this the strengh of github is not in it’s feature but rather it’s because it offer the largest platform.
Using a federation protocol would allow users to contribute without needing one account per instances.
To be honest, I’m starting to drink the Sourcehut coolaid here. We have a distributed method of interacting with repositories: Email.
Don’t get me wrong, the current user experience of email-based patches and discussion isn’t great because it’s too easy to send a badly formatted patch. But if we invested time in making email patches easier to use (e.g. sending them through a web ui for people who prefer github style PRs) then we could skip all the architectural pains of solutions like forgefed.
I don’t know if email is a good solution.
Having contributed to the linux kernel ( in 2010ish ) may have distorted my perception of the gitmail workflow but it doesn’t seems very accesible and i can’t possibly see a change allowing this to be usable by semi-technical users.
The change would be using Gitmail as the plumbing, and normalising the creation of user-friendly porcelain on top.
E.g. suppose there is a repo foo/bar hosted by a forgejo instance at myinstance.org/foo/bar. Sending an email to [email protected] (or similar) could automatically create a PR and, conversely, opening a PR could send a patch series to the foo/bar mailing list.
We really need something like https://forgefed.org/ !
Running all our own forgejo instance is well and good but this the strengh of github is not in it’s feature but rather it’s because it offer the largest platform. Using a federation protocol would allow users to contribute without needing one account per instances.
To be honest, I’m starting to drink the Sourcehut coolaid here. We have a distributed method of interacting with repositories: Email.
Don’t get me wrong, the current user experience of email-based patches and discussion isn’t great because it’s too easy to send a badly formatted patch. But if we invested time in making email patches easier to use (e.g. sending them through a web ui for people who prefer github style PRs) then we could skip all the architectural pains of solutions like forgefed.
I don’t know if email is a good solution. Having contributed to the linux kernel ( in 2010ish ) may have distorted my perception of the gitmail workflow but it doesn’t seems very accesible and i can’t possibly see a change allowing this to be usable by semi-technical users.
The change would be using Gitmail as the plumbing, and normalising the creation of user-friendly porcelain on top.
E.g. suppose there is a repo foo/bar hosted by a forgejo instance at myinstance.org/foo/bar. Sending an email to [email protected] (or similar) could automatically create a PR and, conversely, opening a PR could send a patch series to the foo/bar mailing list.