Re: [Ksummit-discuss] [PATCH 2/2] code-of-conduct: Strip the enforcement paragraph pending community discussion

[James Bottomley]

On Sat, 2018-10-06 at 21:43 +0000, Tim.Bird@xxxxxxxx wrote:
> > -----Original Message-----
> > From: James Bottomley
> > 
> > Significant concern has been expressed about the responsibilities
> > outlined in the enforcement clause of the new code of
> > conduct.ÂÂSince there is concern that this becomes binding on the
> > release of the 4.19 kernel, strip the enforcement clauses to give
> > the community time to consider and debate how this should be
> > handled.
> > 
> > Signed-off-by: James Bottomley
> > <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
> > ---
> > ÂDocumentation/process/code-of-conduct.rst | 15 ---------------
> > Â1 file changed, 15 deletions(-)
> > 
> > diff --git a/Documentation/process/code-of-conduct.rst
> > b/Documentation/process/code-of-conduct.rst
> > index aa40e34e7785..4dd90987305b 100644
> > --- a/Documentation/process/code-of-conduct.rst
> > +++ b/Documentation/process/code-of-conduct.rst
> > @@ -59,21 +59,6 @@ address, posting via an official social media
> > account, or
> > acting as an appointed
> > Ârepresentative at an online or offline event. Representation of a
> > project may
> > be
> > Âfurther defined and clarified by project maintainers.
> > 
> > -Enforcement
> > -===========
> > -
> > -Instances of abusive, harassing, or otherwise unacceptable
> > behavior may be
> > -reported by contacting the Technical Advisory Board (TAB) at
> > -<tab@xxxxxxxxxxxxxxxxxxxxxxxxxx>. All complaints will be reviewed
> > and
> > -investigated and will result in a response that is deemed
> > necessary and
> > -appropriate to the circumstances. The TAB is obligated to maintain
> > -confidentiality with regard to the reporter of an
> > incident.ÂÂFurther details of
> > -specific enforcement policies may be posted separately.
> 
> I think it's OK to leave the above section, as it doesn't speak to
> enforcement, but rather is just a set of reporting instructions,
> with an assurance of confidentiality.ÂÂThis seems to me not to be
> the objectionable part of this section.
> (IOW, I would omit this removal from the patch).

So I did think about that, but it struck me that with both paragraphs
removed, the current CoC is very similar to the status quo: namely
every subsystem handles their own issues and that's formalised by the
"Our Responsibilities" section.  That also makes me think that whether
we want a centralised channel of reporting or enforcement and what it
should be also ought to be part of the debate.  The TAB was created to
channel community technical input into the Linux Foundation.  That's
not to say it can't provide the reporting and arbitration structure,
but if we're going to do it right we should debate the expansion of its
duties (and powers).

I happen to think that the fact that the TAB cannot compel where it
cannot persuade is a huge strength of the system because it means
there's no power structure to subvert if someone were interested in
using it to try to impose their own viewpoint on the community.  But
that's just my opinion and I did write the TAB charter, so I'm probably
biased in this viewpoint.

James


> If the next part is indeed removed, then maybe the section
> needs to be renamed?
> Â-- Tim
> 
> > -
> > -Maintainers who do not follow or enforce the Code of Conduct in
> > good faith
> > may
> > -face temporary or permanent repercussions as determined by other
> > members of the
> > -projectâs leadership.
> > -
> > ÂAttribution
> > Â===========
> 
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@xxxxxxxxxxxxxxxxxxxxxxxxx
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss