Hi all, As everyone knows by now, we added a new Code of Conduct to the kernel tree a few weeks ago.
When we did this, it raised a number of questions as to how this would affect the kernel community. To help address these issues, I, and a few other kernel developers including the TAB, have come up with the following patch series to be added to the tree to both modify the existing Code of Conduct to remove a confusing paragraph as well as to add a new document to help explain how the Code of Conduct is to be interpreted by our community. I originally sent the first two patches in this series to a lot of kernel developers privately, to get their review and comments and see if they wanted to ack them. This is the traditional way we have always done for policy documents or other "contentious" issues like the GPLv3 statement or the "closed kernel modules are bad" statement. Due to the very unexpected way that the original Code of Conduct file was added to the tree, a number of developers asked if this series could also be posted publicly before they were merged, and so, here they are. This patch series adds this new document to the kernel tree, as well as removes a paragraph from the existing Code of Conduct that was bothersome to many maintainers. It also does a bit of housekeeping around these documents to get the documentation links correct as well as fix up the email address and other links and add a MAINTAINER entry for the files. Also I would like to publicly thank Mishi Choudhary for being willing to serve as a mediator for Code of Conduct issues. She has a long history of working in many open source communities, many much more contentious than ours. For more information about her, please see her wikipedia entry: https://en.wikipedia.org/wiki/Mishi_Choudhary or take the chance to talk with her at the Plumbers conference in a few weeks, as she will be attending that along with almost everyone on the TAB as well as many kernel developers and maintainers, myself included. thanks, greg k-h Chris Mason (1): Code of conduct: Fix wording around maintainers enforcing the code of conduct Greg Kroah-Hartman (6): Code of Conduct Interpretation: Add document explaining how the Code of Conduct is to be interpreted Code of Conduct Interpretation: Properly reference the TAB correctly Code of Conduct: Provide links between the two documents Code of Conduct Interpretation: Put in the proper URL for the committee Code of Conduct: Change the contact email address MAINTAINERS: Add an entry for the code of conduct .../code-of-conduct-interpretation.rst | 156 ++++++++++++++++++ Documentation/process/code-of-conduct.rst | 25 +-- Documentation/process/index.rst | 1 + MAINTAINERS | 6 + 4 files changed, 178 insertions(+), 10 deletions(-) create mode 100644 Documentation/process/code-of-conduct-interpretation.rst -- 2.19.1