Re: [PATCH] Documentation/CoC: spell out enforcement for unacceptable behaviors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/11/24 15:35, Laurent Pinchart wrote:
Hi Shuah,

On Mon, Nov 11, 2024 at 02:50:45PM -0700, Shuah Khan wrote:
On 11/11/24 13:07, Simona Vetter wrote:
On Fri, Nov 08, 2024 at 09:18:53AM -0700, 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>

I think it's really good to document these details. The freedesktop coc
team is going through the same process, we've also done a talk at XDC
about all these changes, and I think this helps a lot in transparency and
accountability in practice. With that, some thoughts below.

I've been thinking about replying to this patch for a few days now. I
think I managed to sleep over it enough to make that possible.

I share Sima's opinion here. There is FUD around the CoC and its
enforcement process due to lack of transparency, so I believe
documenting the goals and means is important and will help.


Thank you for your feedback.

Thank you Simona for your review and feedback.

---
   .../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
+*************************************
+
+The Code of Conduct Committee publicly calls out the behavior in the
+setting in which the violation has taken place, seeking public apology
+for the violation.
+
+A public apology for the violation is the first step towards rebuilding
+the trust. Trust is essential for the continued success and health of the
+community which operates on trust and respect.

Personal take, but I think a forced public apology as the primary or at
least initial coc enforcement approach is one of the worst.

Seeking public apology is in response to unacceptable behaviors which are
serious in nature. These incidents are exceedingly rare. When these incidents
happen, they usually resolve when another developer/community member points
out the behavior. The individual responds with a voluntary apology to
mend fences and repair harm.

The CoC  gets involved only when it receives a report which is the case
when normal paths such as peers pointing out the behavior to repair the
harm haven't been successful.

This document isn't intended to be a complete summary of all actions the
CoC takes in response to reports. There is a lot of back and forth with
the individuals to bring about change before the CoC asks for an apology.


See below clarification on above use of "actions"

The CoC seeks public apology only when it is essential to repair the harm.

Limiting the CoC committee to seeking public apology, due to what it
means in terms of both process and goal, would deprive the committee
from many useful courses of action. I was expecting you were not limited
to this, and I appreciate that you are stating it clearly here. It is
not however clear from this patch, and I believe it would benefit the
whole community if this was explained better in the document. A more
detailed description of the different means of action and outcomes would
help balance the fact that the proceedings of the CoC committe are not
public.
The actions CoC takes prior asking for a public apology are working
with the individual to bring about change in their understanding the
importance to repair damage caused by the behavior.

Since these are measures to bring about change, the document doesn't
go into the details about the logistics.

If you have other possible courses of action in mind, please do state
them.

I would like to add that I appreciate the emphasis on rebuilding trust
as a goal, as I also believe trust and respect are essential. This
includes trust that victims will receive the support and protection they
need, trust that authors of behaviour deemed unfit by the community will
be treated fairly, and trust that the community will continuously work
on improving inclusiveness. All three aspects are needed to avoid
driving current and prospective community members away.

First, a ban or temporary suspension seems too mechanical and not in
proportion with the offence of failing to apologize. In my enforcement
thus far as maintainer and now also freedesktop.org CoC member we only use
punishment if behavior has failed to change _and_ we need to protect the
community from further harm. Usually it takes years to get to that point,
unless in extremely severe cases (like public harrassment campaigns) or
when the person stated that they refuse to even consider changing behavior
at all.

Please see above. Public apology is necessary to repair and restore the
health of the community in these rare cases when an individual doesn't
understand that their behavior could cause harm. The CoC tries to get
the individual to realize that offering a public apology is necessary
to repair the harm and resume respectful and productive discussions.

Public means you're amping up the stakes and massively increase the odds
of people being afraid of their reputation and losing face. In my
experience people are a lot more reasonable when you discuss their
behavior and what needs to change in private. This even includes the case
where a temporary suspension had to be put in place already first, to
protect others.

Please see above. The CoC works with the individual prior to taking the step
of asking for an apology. It is a balancing act between repairing
the harm caused to the individuals at the receiving end of the public
unacceptable behavior and working with the individual to understand the
harm done by such a behavior.

The CoC is mindful of the negative impact of seeking public apology and
instituting ban could have on individuals.

It could also be worth adding that, as Sima pointed out below, public
apology is sometimes not the best option for the victim.

The CoC takes these into consideration during the investigation,
before determining the best course of action.

Some people may
be afraid to report bad behaviours if they thought that the story would
be made public by a requirement to apologize publicly. I have total
confidence that the CoC committee will consult with the victim to
determine the best course of action, and that is worth documenting
explicitly.


Thank you for your confidence in the CoC.

Please note that the CoC has the obligation to keep the reports
and individual information private. This public apology is specific
to a public violation that has taken place on a public email list.
The information and details are already public.

The CoC could receive reports from a community member who could be
an observer and not the victim. The CoC has the responsibility to
investigate all such public violations.

The CoC has the obligation to keep the reports privates. The public
part is where the individual who violated the agreed upon Code of
Conduct is asked to apologize to in response to the thread in which
the violation has taken place.

thanks,
-- Shuah








[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux