Slashdot Mirror

← Back to Stories (view on slashdot.org)

Linux Kernel Adopts 'Code of Conflict'

Posted by Soulskill on from the be-excellent-to-each-other dept.

Motor was one of several readers to note that a small patch recently added to the Linux kernel contains guidelines for discourse and dispute resolution within the community. It's called the "Code of Conflict." Quoting: Your code and ideas behind it will be carefully reviewed, often resulting in critique and criticism. The review will almost always require improvements to the code before it can be included in the kernel. Know that this happens because everyone involved wants to see the best possible solution for the overall success of Linux. .... If however, anyone feels personally abused, threatened, or otherwise uncomfortable due to this process, that is not acceptable. ... As a reviewer of code, please strive to keep things civil and focused on the technical issues involved.

2 of 93 comments (clear)

  1. The full text by phantomfive · · Score: 4, Informative
    Linus himself merged it. To me it looks like standard HR CYA legal language, but at least it quotes Bill & Ted.

    The Linux kernel development effort is a very personal process compared to "traditional" ways of developing software. Your code and ideas behind it will be carefully reviewed, often resulting in critique and criticism. The review will almost always require improvements to the code before it can be included in the kernel. Know that this happens because everyone involved wants to see the best possible solution for the overall success of Linux. This development process has been proven to create the most robust operating system kernel ever, and we do not want to do anything to cause the quality of submission and eventual result to ever decrease.

    If however, anyone feels personally abused, threatened, or otherwise uncomfortable due to this process, that is not acceptable. If so, please contact the Linux Foundation's Technical Advisory Board at , or the individual members, and they will work to resolve the issue to the best of their ability. For more information on who is on the Technical Advisory Board and what their role is, please see: http://www.linuxfoundation.org...

    As a reviewer of code, please strive to keep things civil and focused on the technical issues involved. We are all humans, and frustrations can be high on both sides of the process. Try to keep in mind the immortal words of Bill and Ted, "Be excellent to each other."

    --
    "First they came for the slanderers and i said nothing."
    1. Re:The full text by martiniturbide · · Score: 4, Informative

      I think that Wil Wheaton advice is also good for this kind of conflict situation:
      https://dontbeadickday.com/

      It even has a "simple chart" to explain it.