@sir GitHub added a UI to edit files on the web, which automatically creates a fork and opens the pull-request form.
It's not so great for editing code, but it's perfect for small changes.
@val those changes are almost always worthless, though. They generally don't build, have style errors, etc. I've repeatedly asked GitHub to give me a knob to disable this with
@sir Setting up git sendmail requires being able send mail via the sendmail binary, or via an SMTP port (25, 465, 587), which is not something a lot of people have these days. Compared to that, the hoops GitHub makes one jump through are much simpler.
Much as I hate it.
@liw wait, who doesn't have SMTP access?
@sir A lot of people. Most people use webmail of some sort, not SMTP and IMAP clients, for example.
@liw their email provider almost certainly provides SMTP access.
@sir Arranging for that is much more work than using GitHub, though. Been there, done that. Several times. Not going to debate this. Your lived experience is clearly far different from mine.
@liw @jhulten here's what I'm getting at: if you intend to write code, you should be comfortable learning new technology things and looking up docs. If you are, then figuring out SMTP is not hard. You just have to find a few magic strings and plug them into the right places, and tutorials telling you Googleable names of those magic strings and exactly where to put them exist.
@liw @sir Especially when the comparison is to Github or even Gitlab. The simplest case I can see is a documentation fix. With either GH or GL, a local checkout is not required. This is a serious low bar to clear.
If all you care about is people that write code like you write, maybe you are right. But most new contributors start small to learn and to see how the community reacts to their input.
I'm currently postmastering for a large organisation, and I spend as long as possible trying to get developers to STOP SENDING EMAIL from their systems. An email is rarely the right answer when compared to an actual API call (even if that's only an HTTPS POST).
Even internally, email is NOT RELIABLE due to the number of defences we have to put inline due to constant egregious misuse by criminal groups (e.g. spam, malware, compromised accounts, etc etc.).
@sir @liw Simply processing SMTP transactions isn't difficult. But when you look at the problem from a higher level of "who/what is communicating and who/what is supposed to be receiving" then if it isn't a human talking to a human (and even then) email is probably not the right system in the first place.
cmpwn.com is a private Mastodon instance for friends of SirCmpwn.