>; what about developers who refuse to use the email-based process? I guess I don't understand your question. In Linux, the email-as-the-workflow[1] has been

>; what about developers who refuse to use the email-based process? I guess I don't understand your question. In Linux, the email-as-the-workflow[1] has been agreed upon from Linux Torvald and his lieutenants all the way down. I suppose that if a one refused to use email-based-workflow, they'd have to find a Linux kernel maintainer to be a champion for their proposed changes and submit them on their behalf. (Is this a common scenario? I don't know.) If a rebel Linux kernel programmer insisted on staging changes for review in Gerritt/JIRA/github/etc, he's going to be isolated in an island because he's not part of the agreed-upon workflow: emails. [1] https://github.com/torvalds/linux/blob/master/Documentation/process/submitting-patches.rst#14-the-canonical-patch-format https://github.com/torvalds/linux/blob/master/Documentation/...