Just a dude on the fediverse. More on my personal website
Well I've been a part of the Sourcehut (one of his major projects) community for many years and have interacted with him many many times. I've never found him to be a drama queen. Is he outspoken? Yea. Does he stand up for what he believes in? Yea. So he usually goes against the grain and catches flack for it.
His last article, which is referenced in the current article, gives context:
This is ideal for me. I refuse to use Discord period and only use Slack only for direct client work (when they request that we use it.)
Mailing lists are great imho but I'm older than most people probably on these communities. So I'm very familiar with this.
I do think a ticket tracker is useful/required though.
At this point, who cares when LibreOffice exists? Though I do get the potential confusion for newbies but there is so much written out there on this topic I feel like it's harder and harder to get confused on the two.
I’d have to read a guide on how to send a patch or apply one from somebody else.
The guide is about 2 paragraphs and you'd also have to read a guide for how to create an account, fork, clone, push, send PR, etc. for the new normal workflow.
Commenting on a line of code and following a discussion about it isn’t very legible.
It's normal email bottom posting usually, pretty simple to follow. The srht UI does a decent job of this for you as well imho.
There’s no way to mark a discussion as resolved, now way to have a quick overview of the status of all the comments left on a patch
In email specifically, no. Of course you can mark it resolved if using custom software (ie, srht) that supports it. Not sure what you mean of quick overview, unless you mean via a webpage which again, srht provides. If straight email, you have to cycle through the emails. Which for me, just means typing "j" or "k" instead of page up/down like you would on GH, srht, whatever.
is it possible to submit a patch with multiple commits and if so how does one see the final result?
Yes, of course. No clue about seeing them all in one final patch. I suppose that's useful though I've never had an issue going through each patch individually. Maybe a feature suggestion for srht.
Is it possible to sign my commits?
I don't see why not.
I've used email WF, then "github WF", and found srht very refreshing when it launched. I still stuck with BitBucket because I didn't want to take the time to move over but once they removed Mercurial support, we went all in with srht and no regrets. Our code review process via email is so much faster for us now and prior to this move, I was the only person on the team who'd worked with the email WF before.
Of course, I totally get it's a personal preference and that a lot of younger developers have no experience with the email WF and humans are naturally resistant to change. They probably wouldn't enjoy it either.
Well there are many smaller projects than the kernel that still use the email workflow. To me it's simple, not archaic. You're right though, you definitely would miss out on contributors but that's just the reality of the dev world today.
I hope I never have to look for a job again but with the way my business has gone lately, I may need to start thinking about it in a few years.
I've also been coding for 25 years, most of that professionally. I'm not sure I could pass a tech interview.
This is what I love about it. Also email is used in the biggest projects in the world (including the linux kernel). It allows anyone to just clone & contribute immediately.
We run our own SourceHut instance because I hate all the social dopamine crap built into GH. I hate you need an account just to participate in a repo. I hate the heavy UI (sometimes it's better than others).
Also, srht supports hg as well as git.
You wrote my comment. Love to see the email work flow promoted but I am pretty confused with ayllu