4 ms·
Don't particularly agree with the tone of this "advertorial" but I agree that the issue of the ecosystem becoming excessively github-centric is real. I wish Gi
by toyg 6y ago
Don't particularly agree with the tone of this "advertorial" but I agree that the issue of the ecosystem becoming excessively github-centric is real.
I wish Github, Gitlab, sourcehut and (why not) Atlassian, would sit down and hash out a bunch of formats and protocols that make it easy to collaborate across and off them. A galaxy of tools, with everyone using their favorite one, would be a fabulous step forward for developers everywhere.
I know it's not going to happen anytime soon, but one can dream.
- kanox 6y agoIt's already trivial to move code between git service providers, or even run your own. Code review and issue trackers are harder because they're effectively forums are only useful when centralized.
- mikepurvis 6y agoGitLab has been at least tracking federated instances as a wishlist item since 2018, and it was marked for a time as "Vision FY20": https://gitlab.com/gitlab-org/gitlab/-/issues/6468 https://gitlab.com/gitlab-org/gitlab/-/issues/6468 I doubt that GitHub would have much incentive to come to the table on any of this, but if GitLab can at least figure it out between instances of itself, it seems likely that sr.ht and BitBucket would be motivated to implement whatever the system is, and eventually social pressure would force GitHub to cooperate with it as well.
- bccdee 6y agoYeah I think there's a strange focus on vindicating plain-text email in that article instead of criticizing GitHub for being a closed ecosystem. Plain-text email is kind of a huge pain in the ass to use, and the PR web GUI system is nice. The focus should be on interoperable PRs, not resurrecting plain-text email.
- sreevisakh 6y agoI started trying out the plaintext email workflow recently. One thing is very clear - all that pain is only because of bad tools and nothing to do with workflow itself. Regular email clients (incl webclients) garble the workflow horribly - HTML by default, top posting with no easy way to correct it, and attachment handling that assumes the user to be an idiot. I use neomutt. It's hard to learn and it's not the best an email client can be. But it makes git-email workflow and mailing list handling much more pleasant. There is more that can be done. Better GUI and web clients for plain text email can help. Clients can display issue threads better. Patch mails can be combined. There can be an interface to import the patches easily. There can be optional markdown/ReST/asciidoc rendering. Similar improvements can be made with mailing lists too. With good tools, email workflow can be more pleasant and more intuitive than Fork-PR.
- sreevisakh 6y agoThe 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 agoSMTP 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.
- pabs3 6y agoThere is a plan for that called ForgeFed, not sure if GitHub is involved in that or not though. https://forgefed.peers.community/ https://forgefed.peers.community/ https://news.ycombinator.com/item?id=23572576 https://news.ycombinator.com/item?id=23572576