Documentation/process/code-of-conduct-interpretation.rst

8 open-source community is unique and the Linux kernel is no exception.
11 to be static over time, and will adjust it as needed.
14 to "traditional" ways of developing software.  Your contributions and
16 critique and criticism.  The review will almost always require
21 system kernel ever, and we do not want to do anything to cause the
22 quality of submission and eventual result to ever decrease.
29 subsystem, driver, or file, and is listed in the MAINTAINERS file in the
35 The Code of Conduct mentions rights and responsibilities for
36 maintainers, and this needs some further clarifications.
38 First and foremost, it is a reasonable expectation to have maintainers
41 That being said, our community is vast and broad, and there is no new
44 responsibility is upon all of us, and ultimately the Code of Conduct
48 Maintainers should be willing to help when problems occur, and work with
57 everybody.  We know everyone is human and we all fail at times, but the
62 Our goal of creating a robust and technically advanced operating system
63 and the technical complexity involved naturally require expertise and
67 is determined mainly by context and technical complexity and only
68 secondary by the expectations of contributors and maintainers.
70 Both the expertise expectations and decision-making are subject to
73 hands of maintainers and project's leadership and is expected to be used
76 As a consequence, setting expertise expectations, making decisions and
83 the Code of Conduct.  The kernel community is aware of that and provides
96 Developers who use the kernel.org bugzilla, and other subsystem bugzilla
106 addresses, and associated comments in mailing list messages, kernel
110 forums and is in general not covered by the Code of Conduct.  Exceptions
133 use to address reports is varied and will depend on the individual
142 processes (see above) and consults with the TAB as needed and
143 appropriate, for instance to request and receive information about the
154 At quarterly intervals, the Code of Conduct Committee and TAB will
156 Conduct committee has received and their status, as well details of any
157 TAB approved decisions including complete and identifiable voting details.
159 Because how we interpret and enforce the Code of Conduct will evolve over
167 to be inclusive and fosters diverse discussions and viewpoints, and works
170 the development process and maintainers' roles, responsibilities, and their
172 clarification of the development process and the scope of the Code of Conduct.
175 period of time and negatively impact the health of the community longer term.
177 behavior and make amends for it in the setting the violation has taken place.
181 Conduct committee takes measures to restore productive and respectful
185 The Code of Conduct Committee has the obligation to keep the reports and
187 and community members who are observers of unacceptable behaviors. The
188 Code of Conduct Committee has the responsibility to investigate and resolve
193 by their behavior to the injured party and the long term negative impact
209 the trust. Trust is essential for the continued success and health of the
210 community which operates on trust and respect.
226     a. denying patch contributions and pull requests
228        contributions and/or blocking their email account(s)
230        such as mailing lists and social media sites
235 with the community, maintainers, sub-maintainers, and kernel.org
240 public apology and instituting ban could have on individuals. It is also
245 on the trust and cooperation from the community, maintainers, sub-maintainers,
246 and kernel.org administrators in enforcing them.