Hi-- On 11/8/24 8:18 AM, Shuah Khan wrote: > 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@xxxxxxxxxxxxxxxxxxxx> > Acked-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > Acked-by: Miguel Ojeda <ojeda@xxxxxxxxxx> > Acked-by: Dave Hansen <dave.hansen@xxxxxxxxxxxxxxx> > Acked-by: Jonathan Corbet <corbet@xxxxxxx> > Acked-by: Steven Rostedt <rostedt@xxxxxxxxxxx> > Acked-by: Dan Williams <dan.j.williams@xxxxxxxxx> > Signed-off-by: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx> > --- > .../code-of-conduct-interpretation.rst | 52 +++++++++++++++++++ > 1 file changed, 52 insertions(+) > > diff --git a/Documentation/process/code-of-conduct-interpretation.rst b/Documentation/process/code-of-conduct-interpretation.rst > index 66b07f14714c..21dd1cd871d2 100644 > --- a/Documentation/process/code-of-conduct-interpretation.rst > +++ b/Documentation/process/code-of-conduct-interpretation.rst > @@ -156,3 +156,55 @@ overridden decisions including complete and identifiable voting details. > Because how we interpret and enforce the Code of Conduct will evolve over > time, this document will be updated when necessary to reflect any > changes. > + > +Enforcement for Unacceptable Behavior Code of Conduct Violations > +---------------------------------------------------------------- > + > +The Code of Conduct committee works to ensure that our community continues > +to be inclusive and fosters diverse discussions and viewpoints, and works > +to improve those characteristics over time. The Code of Conduct committee > +takes measures to restore productive and respectful collaboration when an > +unacceptable behavior has negatively impacted that relationship. > + > +Seek public apology for the violation > +************************************* > + According to Documentation/doc-guide/sphinx.rst, kernel documentation tries to use "~~~~~~~~~~~~~~~~~~~" for subsections (not "******************"). This is not enforced -- it's more of a guideline. Thanks. -- ~Randy
