0001 .. _code_of_conduct_interpretation:
0002
0003 Linux Kernel Contributor Covenant Code of Conduct Interpretation
0004 ================================================================
0005
0006 The :ref:`code_of_conduct` is a general document meant to
0007 provide a set of rules for almost any open source community. Every
0008 open-source community is unique and the Linux kernel is no exception.
0009 Because of this, this document describes how we in the Linux kernel
0010 community will interpret it. We also do not expect this interpretation
0011 to be static over time, and will adjust it as needed.
0012
0013 The Linux kernel development effort is a very personal process compared
0014 to "traditional" ways of developing software. Your contributions and
0015 ideas behind them will be carefully reviewed, often resulting in
0016 critique and criticism. The review will almost always require
0017 improvements before the material can be included in the
0018 kernel. Know that this happens because everyone involved wants to see
0019 the best possible solution for the overall success of Linux. This
0020 development process has been proven to create the most robust operating
0021 system kernel ever, and we do not want to do anything to cause the
0022 quality of submission and eventual result to ever decrease.
0023
0024 Maintainers
0025 -----------
0026
0027 The Code of Conduct uses the term "maintainers" numerous times. In the
0028 kernel community, a "maintainer" is anyone who is responsible for a
0029 subsystem, driver, or file, and is listed in the MAINTAINERS file in the
0030 kernel source tree.
0031
0032 Responsibilities
0033 ----------------
0034
0035 The Code of Conduct mentions rights and responsibilities for
0036 maintainers, and this needs some further clarifications.
0037
0038 First and foremost, it is a reasonable expectation to have maintainers
0039 lead by example.
0040
0041 That being said, our community is vast and broad, and there is no new
0042 requirement for maintainers to unilaterally handle how other people
0043 behave in the parts of the community where they are active. That
0044 responsibility is upon all of us, and ultimately the Code of Conduct
0045 documents final escalation paths in case of unresolved concerns
0046 regarding conduct issues.
0047
0048 Maintainers should be willing to help when problems occur, and work with
0049 others in the community when needed. Do not be afraid to reach out to
0050 the Technical Advisory Board (TAB) or other maintainers if you're
0051 uncertain how to handle situations that come up. It will not be
0052 considered a violation report unless you want it to be. If you are
0053 uncertain about approaching the TAB or any other maintainers, please
0054 reach out to our conflict mediator, Joanna Lee <joanna.lee@gesmer.com>.
0055
0056 In the end, "be kind to each other" is really what the end goal is for
0057 everybody. We know everyone is human and we all fail at times, but the
0058 primary goal for all of us should be to work toward amicable resolutions
0059 of problems. Enforcement of the code of conduct will only be a last
0060 resort option.
0061
0062 Our goal of creating a robust and technically advanced operating system
0063 and the technical complexity involved naturally require expertise and
0064 decision-making.
0065
0066 The required expertise varies depending on the area of contribution. It
0067 is determined mainly by context and technical complexity and only
0068 secondary by the expectations of contributors and maintainers.
0069
0070 Both the expertise expectations and decision-making are subject to
0071 discussion, but at the very end there is a basic necessity to be able to
0072 make decisions in order to make progress. This prerogative is in the
0073 hands of maintainers and project's leadership and is expected to be used
0074 in good faith.
0075
0076 As a consequence, setting expertise expectations, making decisions and
0077 rejecting unsuitable contributions are not viewed as a violation of the
0078 Code of Conduct.
0079
0080 While maintainers are in general welcoming to newcomers, their capacity
0081 of helping contributors overcome the entry hurdles is limited, so they
0082 have to set priorities. This, also, is not to be seen as a violation of
0083 the Code of Conduct. The kernel community is aware of that and provides
0084 entry level programs in various forms like kernelnewbies.org.
0085
0086 Scope
0087 -----
0088
0089 The Linux kernel community primarily interacts on a set of public email
0090 lists distributed around a number of different servers controlled by a
0091 number of different companies or individuals. All of these lists are
0092 defined in the MAINTAINERS file in the kernel source tree. Any emails
0093 sent to those mailing lists are considered covered by the Code of
0094 Conduct.
0095
0096 Developers who use the kernel.org bugzilla, and other subsystem bugzilla
0097 or bug tracking tools should follow the guidelines of the Code of
0098 Conduct. The Linux kernel community does not have an "official" project
0099 email address, or "official" social media address. Any activity
0100 performed using a kernel.org email account must follow the Code of
0101 Conduct as published for kernel.org, just as any individual using a
0102 corporate email account must follow the specific rules of that
0103 corporation.
0104
0105 The Code of Conduct does not prohibit continuing to include names, email
0106 addresses, and associated comments in mailing list messages, kernel
0107 change log messages, or code comments.
0108
0109 Interaction in other forums is covered by whatever rules apply to said
0110 forums and is in general not covered by the Code of Conduct. Exceptions
0111 may be considered for extreme circumstances.
0112
0113 Contributions submitted for the kernel should use appropriate language.
0114 Content that already exists predating the Code of Conduct will not be
0115 addressed now as a violation. Inappropriate language can be seen as a
0116 bug, though; such bugs will be fixed more quickly if any interested
0117 parties submit patches to that effect. Expressions that are currently
0118 part of the user/kernel API, or reflect terminology used in published
0119 standards or specifications, are not considered bugs.
0120
0121 Enforcement
0122 -----------
0123
0124 The address listed in the Code of Conduct goes to the Code of Conduct
0125 Committee. The exact members receiving these emails at any given time
0126 are listed at https://kernel.org/code-of-conduct.html. Members can not
0127 access reports made before they joined or after they have left the
0128 committee.
0129
0130 The initial Code of Conduct Committee consists of volunteer members of
0131 the TAB, as well as a professional mediator acting as a neutral third
0132 party. The first task of the committee is to establish documented
0133 processes, which will be made public.
0134
0135 Any member of the committee, including the mediator, can be contacted
0136 directly if a reporter does not wish to include the full committee in a
0137 complaint or concern.
0138
0139 The Code of Conduct Committee reviews the cases according to the
0140 processes (see above) and consults with the TAB as needed and
0141 appropriate, for instance to request and receive information about the
0142 kernel community.
0143
0144 Any decisions by the committee will be brought to the TAB, for
0145 implementation of enforcement with the relevant maintainers if needed.
0146 A decision by the Code of Conduct Committee can be overturned by the TAB
0147 by a two-thirds vote.
0148
0149 At quarterly intervals, the Code of Conduct Committee and TAB will
0150 provide a report summarizing the anonymised reports that the Code of
0151 Conduct committee has received and their status, as well details of any
0152 overridden decisions including complete and identifiable voting details.
0153
0154 We expect to establish a different process for Code of Conduct Committee
0155 staffing beyond the bootstrap period. This document will be updated
0156 with that information when this occurs.
