Skip to content

Commit c818d5c

Browse files
shuahkhJonathan Corbet
authored andcommitted
Documentation/CoC: spell out enforcement for unacceptable behaviors
The Code of Conduct committee's goal first and foremost is to bring about change to ensure our community continues to foster respectful discussions. In the interest of transparency, the CoC enforcement policy is formalized for unacceptable behaviors. Update the Code of Conduct Interpretation document with the enforcement information. Acked-by: Linus Torvalds <torvalds@linux-foundation.org> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Acked-by: Miguel Ojeda <ojeda@kernel.org> Acked-by: Dave Hansen <dave.hansen@linux.intel.com> Acked-by: Jonathan Corbet <corbet@lwn.net> Acked-by: Steven Rostedt <rostedt@goodmis.org> Acked-by: Dan Williams <dan.j.williams@intel.com> Acked-by: Theodore Ts'o <tytso@mit.edu> Acked-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org> Acked-by: Kees Cook <kees@kernel.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Link: https://lore.kernel.org/r/20241114205649.44179-1-skhan@linuxfoundation.org
1 parent 623e574 commit c818d5c

File tree

1 file changed

+87
-0
lines changed

1 file changed

+87
-0
lines changed

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

Lines changed: 87 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -156,3 +156,90 @@ overridden decisions including complete and identifiable voting details.
156156
Because how we interpret and enforce the Code of Conduct will evolve over
157157
time, this document will be updated when necessary to reflect any
158158
changes.
159+
160+
Enforcement for Unacceptable Behavior Code of Conduct Violations
161+
----------------------------------------------------------------
162+
163+
The Code of Conduct committee works to ensure that our community continues
164+
to be inclusive and fosters diverse discussions and viewpoints, and works
165+
to improve those characteristics over time. A majority of the reports the
166+
Code of Conduct Committee receives stem from incorrect understanding regarding
167+
the development process and maintainers' roles, responsibilities, and their
168+
right to make decisions on code acceptance. These are resolved through
169+
clarification of the development process and the scope of the Code of Conduct.
170+
171+
Unacceptable behaviors could interrupt respectful collaboration for a short
172+
period of time and negatively impact the health of the community longer term.
173+
Unacceptable behaviors often get resolved when individuals acknowledge their
174+
behavior and make amends for it in the setting the violation has taken place.
175+
176+
The Code of Conduct Committee receives reports about unacceptable behaviors
177+
when they don't get resolved through community discussions. The Code of
178+
Conduct committee takes measures to restore productive and respectful
179+
collaboration when an unacceptable behavior has negatively impacted that
180+
relationship.
181+
182+
The Code of Conduct Committee has the obligation to keep the reports and
183+
reporters' information private. Reports could come from injured parties
184+
and community members who are observers of unacceptable behaviors. The
185+
Code of Conduct Committee has the responsibility to investigate and resolve
186+
these reports, working with all involved parties.
187+
188+
The Code of Conduct Committee works with the individual to bring about
189+
change in their understanding of the importance to repair the damage caused
190+
by their behavior to the injured party and the long term negative impact
191+
on the community.
192+
193+
The goal is to reach a resolution which is agreeable to all parties. If
194+
working with the individual fails to bring about the desired outcome, the
195+
Code of Conduct Committee will evaluate other measures such as seeking
196+
public apology to repair the damage.
197+
198+
Seek public apology for the violation
199+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
200+
201+
The Code of Conduct Committee publicly calls out the behavior in the
202+
setting in which the violation has taken place, seeking public apology
203+
for the violation.
204+
205+
A public apology for the violation is the first step towards rebuilding
206+
the trust. Trust is essential for the continued success and health of the
207+
community which operates on trust and respect.
208+
209+
Remedial measures if there is no public apology for the violation
210+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
211+
212+
The Code of Conduct Committee determines the next course of action to restore
213+
the healthy collaboration by recommending remedial measure(s) to the TAB for
214+
approval.
215+
216+
- Ban violator from participating in the kernel development process for
217+
a period of up to a full kernel development cycle. The Code of Conduct
218+
Committee could require public apology as a condition for lifting the
219+
ban.
220+
221+
The scope of the ban for a period of time could include:
222+
223+
a. denying patch contributions and pull requests
224+
b. pausing collaboration with the violator by ignoring their
225+
contributions and/or blocking their email account(s)
226+
c. restricting their ability to communicate via kernel.org platforms,
227+
such as mailing lists and social media sites
228+
229+
Once the TAB approves one or more of the measures outlined in the scope of
230+
the ban by a two-thirds vote, the Code of Conduct Committee will enforce
231+
the TAB approved measure(s) in collaboration with the community, maintainers,
232+
sub-maintainers, and kernel.org administrators.
233+
234+
The Code of Conduct Committee is mindful of the negative impact of seeking
235+
public apology and instituting ban could have on individuals. It is also
236+
mindful of the longer term harm to the community that could result from
237+
not taking action when such serious public violations occur.
238+
239+
The effectiveness of the remedial measure(s) approved by the TAB depends
240+
on the trust and cooperation from the community, maintainers, sub-maintainers,
241+
and kernel.org administrators in enforcing them.
242+
243+
The Code of Conduct Committee sincerely hopes that unacceptable behaviors
244+
that require seeking public apologies continue to be exceedingly rare
245+
occurrences in the future.

0 commit comments

Comments
 (0)