Re: [Ksummit-discuss] [TECH-TOPIC] Review - Code of Conduct: Let's revamp it.

[James Bottomley <James.Bottomley@HansenPartnership.com>]

On Fri, 2018-10-05 at 12:10 -0600, Shuah Khan wrote:
> On 10/04/2018 10:27 AM, James Bottomley wrote:
> > On Mon, 2018-09-24 at 08:24 -0600, Shuah Khan wrote:
> > > I have been trying to follow various threads on this topic and
> > > none of them address the review of this patch that went in. There
> > > is no mistake in the title of this topic. I do consider this
> > > topic to be more general than limited to Maintainer Summit.
> > > Hence, the choice of a wider Technical designation.
> > > 
> > > So I am kicking off a thread to do the review with my comments. I
> > > am in general agreement with the spirit of this change to the
> > > existing "Code of Conflict".
> > 
> > Just as an FYI, the Zephyr project recently included the
> > contributor covenant CoC minus the enforcement clause.  They did a
> > standard github PR for this:
> > 
> > https://github.com/zephyrproject-rtos/zephyr/pull/10356
> > 
> > They note that they may add more enforcement details when the
> > community agrees on them.
> > 
> 
> Thanks for the link. It is almost identical to the Code of Conduct
> that went into Linux 4.19-rc4 minus the enforcement section.
> 
> It would make sense to remove the enforcement section and discuss and
> add enforcement after the usual patch review process we already have
> in place.
> 
> I personally would prefer amending the CoC in Linux 4.19 removing the
> enforcement details over waiting to discuss at the Maintainer and/or
> Kernel summit and releasing Linux 4.19 with the CoC v1 as it reads
> now.

OK, I took this suggestion and posted it as a concrete patch set to see
how it flies.

James