The answer to "is sr.ht and/or mailing-list-driven development harder for drive-by contributors than GitHub?"

sr.ht/7uuK.txt

@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.

@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 @liw Which requires understanding of where to find the information and how to authenticate.

@jhulten @liw if they can't google their email provder's SMTP help page then they're in for a bad time with the rest of git

@sir @jhulten I think you're being more than a little arrogant and disingenuous with this requirement that to use git one must have also have, and know how to use, an SMTP provider.

Or in claiming that only "engineer" should use git.

@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 @jhulten and I don't believe in making coding more accessible to people who aren't willing to read docs or solve problems they aren't familiar with. Those are essential, indespensible, non-negotiable skills in the toolbox of a developer.

Follow

@sir @liw I don't believe in forcing people into yak shaving exercises as a form of gatekeeping.

@jhulten @liw if anyone's being disingenous here this is it

Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either! We adhere to an adapted version of the TootCat Code of Conduct and have documented a list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators. Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!