4 ms·

The gist of the article is that protocol you want already exists and is integrated into git- email. Everything that people complain about that workflow (barrie

The gist of the article is that protocol you want already exists and is integrated into git- email. Everything that people complain about that workflow (barrier to entry, initial setup and difficulty to track) is merely because the tools are primitive and unpolished. We wouldn't be considering the Fork-PR workflow if even a fraction of effort that was spent on improving the email workflow tools. There is no reason why email workflow can't be easier than Fork-PR. Consider this - sourcehut is only a pretty interface to discover projects. You don't need to create an account to contribute to the project. You can collaborate even if everything other than the mailing list is down (even that can be overcome). How can Github/lab surpass that even if they bolt on a federation protocol on top of their PR-Fork model?

rfoo 6y ago
> merely because the tools are primitive and unpolished Sorry, but I believe this is the evidence that it's the abstractions behind these tools being primitive and these tools can't be polished, putting more efforts on an impossible task does not help. OT but I guess after Black Lives Matter we should have Noob Lives Matter.
- sreevisakh 6y ago
  SMTP is just a protocol to exchange information. It's no more primitive than the mechanisms that power fork-PR workflow. What makes it impossible for a client to display issue threads and patches like Github does? What makes it impossible to import patches directly from client into a git repository? What makes it impossible to design a simple utility to 'push' a git branch as a set of patches? If the evidence for that is the current state of affairs, I consider it simply as a result of no one having an incentive to invest in a non-centralized workflow - that's not a proof of it being unviable. Making it noob-friendly takes work that nobody has yet put in.

rfoo 6y ago

> merely because the tools are primitive and unpolished Sorry, but I believe this is the evidence that it's the abstractions behind these tools being primitive and these tools can't be polished, putting more efforts on an impossible task does not help. OT but I guess after Black Lives Matter we should have Noob Lives Matter.

sreevisakh 6y ago
SMTP is just a protocol to exchange information. It's no more primitive than the mechanisms that power fork-PR workflow. What makes it impossible for a client to display issue threads and patches like Github does? What makes it impossible to import patches directly from client into a git repository? What makes it impossible to design a simple utility to 'push' a git branch as a set of patches? If the evidence for that is the current state of affairs, I consider it simply as a result of no one having an incentive to invest in a non-centralized workflow - that's not a proof of it being unviable. Making it noob-friendly takes work that nobody has yet put in.