code-of-conduct-interpretation.rst (7399B)
1.. _code_of_conduct_interpretation: 2 3Linux Kernel Contributor Covenant Code of Conduct Interpretation 4================================================================ 5 6The :ref:`code_of_conduct` is a general document meant to 7provide a set of rules for almost any open source community. Every 8open-source community is unique and the Linux kernel is no exception. 9Because of this, this document describes how we in the Linux kernel 10community will interpret it. We also do not expect this interpretation 11to be static over time, and will adjust it as needed. 12 13The Linux kernel development effort is a very personal process compared 14to "traditional" ways of developing software. Your contributions and 15ideas behind them will be carefully reviewed, often resulting in 16critique and criticism. The review will almost always require 17improvements before the material can be included in the 18kernel. Know that this happens because everyone involved wants to see 19the best possible solution for the overall success of Linux. This 20development process has been proven to create the most robust operating 21system kernel ever, and we do not want to do anything to cause the 22quality of submission and eventual result to ever decrease. 23 24Maintainers 25----------- 26 27The Code of Conduct uses the term "maintainers" numerous times. In the 28kernel community, a "maintainer" is anyone who is responsible for a 29subsystem, driver, or file, and is listed in the MAINTAINERS file in the 30kernel source tree. 31 32Responsibilities 33---------------- 34 35The Code of Conduct mentions rights and responsibilities for 36maintainers, and this needs some further clarifications. 37 38First and foremost, it is a reasonable expectation to have maintainers 39lead by example. 40 41That being said, our community is vast and broad, and there is no new 42requirement for maintainers to unilaterally handle how other people 43behave in the parts of the community where they are active. That 44responsibility is upon all of us, and ultimately the Code of Conduct 45documents final escalation paths in case of unresolved concerns 46regarding conduct issues. 47 48Maintainers should be willing to help when problems occur, and work with 49others in the community when needed. Do not be afraid to reach out to 50the Technical Advisory Board (TAB) or other maintainers if you're 51uncertain how to handle situations that come up. It will not be 52considered a violation report unless you want it to be. If you are 53uncertain about approaching the TAB or any other maintainers, please 54reach out to our conflict mediator, Mishi Choudhary <mishi@linux.com>. 55 56In the end, "be kind to each other" is really what the end goal is for 57everybody. We know everyone is human and we all fail at times, but the 58primary goal for all of us should be to work toward amicable resolutions 59of problems. Enforcement of the code of conduct will only be a last 60resort option. 61 62Our goal of creating a robust and technically advanced operating system 63and the technical complexity involved naturally require expertise and 64decision-making. 65 66The required expertise varies depending on the area of contribution. It 67is determined mainly by context and technical complexity and only 68secondary by the expectations of contributors and maintainers. 69 70Both the expertise expectations and decision-making are subject to 71discussion, but at the very end there is a basic necessity to be able to 72make decisions in order to make progress. This prerogative is in the 73hands of maintainers and project's leadership and is expected to be used 74in good faith. 75 76As a consequence, setting expertise expectations, making decisions and 77rejecting unsuitable contributions are not viewed as a violation of the 78Code of Conduct. 79 80While maintainers are in general welcoming to newcomers, their capacity 81of helping contributors overcome the entry hurdles is limited, so they 82have to set priorities. This, also, is not to be seen as a violation of 83the Code of Conduct. The kernel community is aware of that and provides 84entry level programs in various forms like kernelnewbies.org. 85 86Scope 87----- 88 89The Linux kernel community primarily interacts on a set of public email 90lists distributed around a number of different servers controlled by a 91number of different companies or individuals. All of these lists are 92defined in the MAINTAINERS file in the kernel source tree. Any emails 93sent to those mailing lists are considered covered by the Code of 94Conduct. 95 96Developers who use the kernel.org bugzilla, and other subsystem bugzilla 97or bug tracking tools should follow the guidelines of the Code of 98Conduct. The Linux kernel community does not have an "official" project 99email address, or "official" social media address. Any activity 100performed using a kernel.org email account must follow the Code of 101Conduct as published for kernel.org, just as any individual using a 102corporate email account must follow the specific rules of that 103corporation. 104 105The Code of Conduct does not prohibit continuing to include names, email 106addresses, and associated comments in mailing list messages, kernel 107change log messages, or code comments. 108 109Interaction in other forums is covered by whatever rules apply to said 110forums and is in general not covered by the Code of Conduct. Exceptions 111may be considered for extreme circumstances. 112 113Contributions submitted for the kernel should use appropriate language. 114Content that already exists predating the Code of Conduct will not be 115addressed now as a violation. Inappropriate language can be seen as a 116bug, though; such bugs will be fixed more quickly if any interested 117parties submit patches to that effect. Expressions that are currently 118part of the user/kernel API, or reflect terminology used in published 119standards or specifications, are not considered bugs. 120 121Enforcement 122----------- 123 124The address listed in the Code of Conduct goes to the Code of Conduct 125Committee. The exact members receiving these emails at any given time 126are listed at https://kernel.org/code-of-conduct.html. Members can not 127access reports made before they joined or after they have left the 128committee. 129 130The initial Code of Conduct Committee consists of volunteer members of 131the TAB, as well as a professional mediator acting as a neutral third 132party. The first task of the committee is to establish documented 133processes, which will be made public. 134 135Any member of the committee, including the mediator, can be contacted 136directly if a reporter does not wish to include the full committee in a 137complaint or concern. 138 139The Code of Conduct Committee reviews the cases according to the 140processes (see above) and consults with the TAB as needed and 141appropriate, for instance to request and receive information about the 142kernel community. 143 144Any decisions by the committee will be brought to the TAB, for 145implementation of enforcement with the relevant maintainers if needed. 146A decision by the Code of Conduct Committee can be overturned by the TAB 147by a two-thirds vote. 148 149At quarterly intervals, the Code of Conduct Committee and TAB will 150provide a report summarizing the anonymised reports that the Code of 151Conduct committee has received and their status, as well details of any 152overridden decisions including complete and identifiable voting details. 153 154We expect to establish a different process for Code of Conduct Committee 155staffing beyond the bootstrap period. This document will be updated 156with that information when this occurs.