159 lines · plain
1.. _code_of_conduct_interpretation:2 3Linux Kernel Contributor Covenant Code of Conduct Interpretation4================================================================5 6The :ref:`code_of_conduct` is a general document meant to7provide a set of rules for almost any open source community. Every8open-source community is unique and the Linux kernel is no exception.9Because of this, this document describes how we in the Linux kernel10community will interpret it. We also do not expect this interpretation11to be static over time, and will adjust it as needed.12 13The Linux kernel development effort is a very personal process compared14to "traditional" ways of developing software. Your contributions and15ideas behind them will be carefully reviewed, often resulting in16critique and criticism. The review will almost always require17improvements before the material can be included in the18kernel. Know that this happens because everyone involved wants to see19the best possible solution for the overall success of Linux. This20development process has been proven to create the most robust operating21system kernel ever, and we do not want to do anything to cause the22quality of submission and eventual result to ever decrease.23 24Maintainers25-----------26 27The Code of Conduct uses the term "maintainers" numerous times. In the28kernel community, a "maintainer" is anyone who is responsible for a29subsystem, driver, or file, and is listed in the MAINTAINERS file in the30kernel source tree.31 32Responsibilities33----------------34 35The Code of Conduct mentions rights and responsibilities for36maintainers, and this needs some further clarifications.37 38First and foremost, it is a reasonable expectation to have maintainers39lead by example.40 41That being said, our community is vast and broad, and there is no new42requirement for maintainers to unilaterally handle how other people43behave in the parts of the community where they are active. That44responsibility is upon all of us, and ultimately the Code of Conduct45documents final escalation paths in case of unresolved concerns46regarding conduct issues.47 48Maintainers should be willing to help when problems occur, and work with49others in the community when needed. Do not be afraid to reach out to50the Technical Advisory Board (TAB) or other maintainers if you're51uncertain how to handle situations that come up. It will not be52considered a violation report unless you want it to be. If you are53uncertain about approaching the TAB or any other maintainers, please54reach out to our conflict mediator, Joanna Lee <jlee@linuxfoundation.org>.55 56In the end, "be kind to each other" is really what the end goal is for57everybody. We know everyone is human and we all fail at times, but the58primary goal for all of us should be to work toward amicable resolutions59of problems. Enforcement of the code of conduct will only be a last60resort option.61 62Our goal of creating a robust and technically advanced operating system63and the technical complexity involved naturally require expertise and64decision-making.65 66The required expertise varies depending on the area of contribution. It67is determined mainly by context and technical complexity and only68secondary by the expectations of contributors and maintainers.69 70Both the expertise expectations and decision-making are subject to71discussion, but at the very end there is a basic necessity to be able to72make decisions in order to make progress. This prerogative is in the73hands of maintainers and project's leadership and is expected to be used74in good faith.75 76As a consequence, setting expertise expectations, making decisions and77rejecting unsuitable contributions are not viewed as a violation of the78Code of Conduct.79 80While maintainers are in general welcoming to newcomers, their capacity81of helping contributors overcome the entry hurdles is limited, so they82have to set priorities. This, also, is not to be seen as a violation of83the Code of Conduct. The kernel community is aware of that and provides84entry level programs in various forms like kernelnewbies.org.85 86Scope87-----88 89The Linux kernel community primarily interacts on a set of public email90lists distributed around a number of different servers controlled by a91number of different companies or individuals. All of these lists are92defined in the MAINTAINERS file in the kernel source tree. Any emails93sent to those mailing lists are considered covered by the Code of94Conduct.95 96Developers who use the kernel.org bugzilla, and other subsystem bugzilla97or bug tracking tools should follow the guidelines of the Code of98Conduct. The Linux kernel community does not have an "official" project99email address, or "official" social media address. Any activity100performed using a kernel.org email account must follow the Code of101Conduct as published for kernel.org, just as any individual using a102corporate email account must follow the specific rules of that103corporation.104 105The Code of Conduct does not prohibit continuing to include names, email106addresses, and associated comments in mailing list messages, kernel107change log messages, or code comments.108 109Interaction in other forums is covered by whatever rules apply to said110forums and is in general not covered by the Code of Conduct. Exceptions111may 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 be115addressed now as a violation. Inappropriate language can be seen as a116bug, though; such bugs will be fixed more quickly if any interested117parties submit patches to that effect. Expressions that are currently118part of the user/kernel API, or reflect terminology used in published119standards or specifications, are not considered bugs.120 121Enforcement122-----------123 124The address listed in the Code of Conduct goes to the Code of Conduct125Committee. The exact members receiving these emails at any given time126are listed at https://kernel.org/code-of-conduct.html. Members can not127access reports made before they joined or after they have left the128committee.129 130The Code of Conduct Committee consists of volunteer community members131appointed by the TAB, as well as a professional mediator acting as a132neutral third party. The processes the Code of Conduct committee will133use to address reports is varied and will depend on the individual134circumstance, however, this file serves as documentation for the135general process used.136 137Any member of the committee, including the mediator, can be contacted138directly if a reporter does not wish to include the full committee in a139complaint or concern.140 141The Code of Conduct Committee reviews the cases according to the142processes (see above) and consults with the TAB as needed and143appropriate, for instance to request and receive information about the144kernel community.145 146Any decisions regarding enforcement recommendations will be brought to147the TAB for implementation of enforcement with the relevant maintainers148if needed. A decision by the Code of Conduct Committee can be overturned149by the TAB by a two-thirds vote.150 151At quarterly intervals, the Code of Conduct Committee and TAB will152provide a report summarizing the anonymised reports that the Code of153Conduct committee has received and their status, as well details of any154overridden decisions including complete and identifiable voting details.155 156Because how we interpret and enforce the Code of Conduct will evolve over157time, this document will be updated when necessary to reflect any158changes.159