<story><title>Email and Git = &lt;3</title><url>https://git-send-email.io/</url></story><parent_chain><item><author>ploum</author><text>Organizations that insists on using a web interface and ever-changing click workflows not only drive away a significant number of very knowledgeable contributors, but they also form a weirdly irrational culture that fetishizes needlessly graphical content, marketing and fake-usability detrimental to learnability and integration with each user workflow.</text></item><item><author>BaculumMeumEst</author><text>I appreciate the effort here, but after learning the workflow and having to get all this set up on a few computers, having to configure git send-mail is honestly just needlessly annoying and absurd.&lt;p&gt;Organizations that insist on using workflows like git send-mail and mailing lists not only drive away a significant number of potential contributors, but they also form a weirdly religious culture that fetishizes needlessly painful process and is incapable of improvement</text></item></parent_chain><comment><author>sneak</author><text>“needlessly graphical” requires a citation when it’s clear that if you use a web GUI for this you address a market of potential contributors that is three to six orders of magnitude larger.&lt;p&gt;srht is really designed for (and thus only really useful for) lone wolf developers who collaborate rarely, if ever, and with a very small number of collaborators who collaborate infrequently.  It is not built for large teams with constant active collaboration, it falls down for this use case.&lt;p&gt;It’s hobby software for hobby users.  (I don’t think this is a bad thing, but you should be aware of the product design goals of its author.)</text></comment>
<story><title>Email and Git = &lt;3</title><url>https://git-send-email.io/</url></story><parent_chain><item><author>ploum</author><text>Organizations that insists on using a web interface and ever-changing click workflows not only drive away a significant number of very knowledgeable contributors, but they also form a weirdly irrational culture that fetishizes needlessly graphical content, marketing and fake-usability detrimental to learnability and integration with each user workflow.</text></item><item><author>BaculumMeumEst</author><text>I appreciate the effort here, but after learning the workflow and having to get all this set up on a few computers, having to configure git send-mail is honestly just needlessly annoying and absurd.&lt;p&gt;Organizations that insist on using workflows like git send-mail and mailing lists not only drive away a significant number of potential contributors, but they also form a weirdly religious culture that fetishizes needlessly painful process and is incapable of improvement</text></item></parent_chain><comment><author>pjerem</author><text>I have no great love for GitHub, I avoid it for my own projects but their official cli client is pretty functional and there are just tons of other clients, graphical or not for GitHub, GitLab etc …&lt;p&gt;I say that as someone who don’t like GitHub, but overall it’s far from the worst tool an employer may impose to its employees.</text></comment>