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