Re:What is a fork, and how GitHub changed its meaning
by juped on Friday May 24, 2019 @04:40PM
(#20005091)
I love how sourcehut complements git rather than parasitizing on it. That is, I can't fault github's ability to be a dumb remote to publish branches to - but once you use it for that, they have a foot in the door for all the prongs of their proprietary lock-in and what is frankly value-subtract. I'm not worried about that with sourcehut because 1) I don't have to go full sourcehut kool-aid unless I want to (in fact, there's actually too little linkage among the components at present), and 2) if I do, then the kool-aid I've bought into is... a mailing list workflow using decades-old standard technology, where the webapp views are optional.
Re:What is a fork, and how GitHub changed its meaning
by instantwhat on Saturday May 25, 2019 @01:03AM
(#20007202)
Friendly pedantry: in that video, you referred to vi as "vee"? :)
Re:What is a fork, and how GitHub changed its meaning
by Sir_Cmpwn on Saturday May 25, 2019 @12:59PM
(#20010037)
Yes, because that's what it's called :)
Re:What is a fork, and how GitHub changed its meaning
by instantwhat on Monday May 27, 2019 @05:30AM
(#20020677)
So you're saying that you don't care what the original author named his software, and you're going to say it your way, just to be different?
Re:What is a fork, and how GitHub changed its meaning
by jasonhansel on Friday May 24, 2019 @08:26PM
(#20006379)
Whoa! This is a great idea. Looking forward to the "real" post; I've also done some work on implementing distributed systems over email, so I'll be sure to give this a look.
Re:What is a fork, and how GitHub changed its meaning
by Ne02ptzero on Sunday May 26, 2019 @08:54PM
(#20018665)
Looks awesome!
https://yukari.sr.ht/aerc-intro.webm
Don't repost this, please, the official aerc announcement is coming in a few weeks.
I'm working on making a UI similar to GitHub's for reviewing patches which is built on email underneath, but can be used entirely on the web. The first step of this became available a few weeks ago, and now email threads are being rendered into a review UI which is similar to GitHub's with inline feedback and such:
https://lists.sr.ht/~philmd/qemu/patches/5556
This page is fairly new and still needs a bit more work towards mobile support, but I hope that gives you some more confidence in the platform. I intend to extend this so that you can also review patches from the web, which will generate emails on the mailing list, and prepare patchsets from the web as well. The end result will be a UI which is remarkably similar to GitHub in terms of usability on the web, but is backed up with distributed technologies and seamlessly integrates with the workflows of devs who would rather use email.
On the whole Sourcehut is actually quite a bit better at responsiveness than GitHub, too. Rather than a dedicated and inferior mobile site, almost all sr.ht pages are responsive and equally capable on all form-factors.