> The reason for why E-Mail based workflows like those used by Linux and Git didn't win over "just host on Git(Hub|Lab)" is because this requires a lot of setup

> The reason for why E-Mail based workflows like those used by Linux and Git didn't win over "just host on Git(Hub|Lab)" is because this requires a lot of setup [...] That's a reasoned recurring argument and my usual answer is: quality vs quantity. More in detail we are not talking about a hello world software for first years of high schools students but large and complex software; if casual contributors do not have a proper email setup or the knowledge to make it it means they probably do not have enough IT knowledge in general to be valuable contributors. Emails are the base of FOSS communication infrastructure together with nntp news, without them there is substantially no free software nor free "ecosystems" so... However there is a point in criticize actual "sorry state" of email development. I know "bigs of IT" do non like mails because they are an open standard that guarantee no lock-in but we as free software users/devs should help newcomers to gain knowledge and tell actual students "go get mbsync/notmuch/emacs/custom scripts for refile/delete afew/IMAPFilter for autorefile, ..." does not help, offer per-coocked solutions does. Something is happening from fish to precooked zsh configs to {doom,prelude,spacemacs,...} emacs config etc but it's still not enough.