Re: [Ksummit-discuss] [MAINTAINER TOPIC FOR KS] CoC and Linus position (perhaps undocumented/closed/limited/invite session)

[<Tim.Bird@sony.com>]

> -----Original Message-----
> From: Mauro Carvalho Chehab
> 
> Em Wed, 19 Sep 2018 13:10:15 -0700
> "Luck, Tony" <tony.luck@intel.com> escreveu:
> 
> > On Wed, Sep 19, 2018 at 04:55:52PM -0300, Mauro Carvalho Chehab wrote:
> > > After re-reading it, I'm pretty sure that, the way it is, publishing
> > > e-mails violate this CoC.
> > >
> > > The thing is that, when it uses the commas there:
> > >
> > > 	"private information, such as a physical or electronic address,"
> > >
> > > The commas actually defines what "private information" is. Even if
> > > this would be changed by "foo information", what we have here is
> actually two
> > > English sentences that were merged together:
> > >
> > > First sentence:
> > > 	"Private information, such as a physical or electronic address."
> > >
> > > Second sentence:
> > > 	"Publishing others’ private information without explicit permission"
> > >
> > > See, replace it by foo at the original text:
> > > 	"Publishing others’ *foo* information, such as a physical
> > > 	 or electronic address, without explicit permission"
> > >
> > > You'll see that "*foo* information" becomes defined.
> >
> > So perhaps we can move on to discussing a patch to fix it?
> >
> >
> > diff --git a/Documentation/process/code-of-conduct.rst
> b/Documentation/process/code-of-conduct.rst
> > index ab7c24b5478c..ec99a17ab646 100644
> > --- a/Documentation/process/code-of-conduct.rst
> > +++ b/Documentation/process/code-of-conduct.rst
> > @@ -31,10 +31,13 @@ Examples of unacceptable behavior by participants
> include:
> >  * Trolling, insulting/derogatory comments, and personal or political attacks
> >  * Public or private harassment
> >  * Publishing others’ private information, such as a physical or electronic
> > -  address, without explicit permission
> > +  address[1], without explicit permission
> >  * Other conduct which could reasonably be considered inappropriate in a
> >    professional setting
> >
> > +[1] Note that e-mail addresses used on public mailing lists are not
> > +considered to be private information and can (in fact should) be used
> > +to give credit in Reported-by, Acked-by, Tested-by etc. tags.
> >
> >  Our Responsibilities
> >  ====================
> 
> Reviewed-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>

This looks like a straightforward way to address the ambiguity.  It does a bit 
of extra social engineering, with the "(in fact should)" part, but personally
I find that OK.

I don't know if the CoC changes are supposed to be considered rather more
cautiously than other changes or not (well - after the initial somewhat rushed
inclusion).  Do you have to wait for a merge window?  What is
the severity of a "bug" in the CoC, and does it merit a quick change or more
slow deliberation?  Who knows? It's up to Greg to decide for the time being I guess.

Luckily this won't break anything in user space, so even if this is not exactly
the fix we're looking for, it's probably not a big deal to accept this now.  ;-)

Anyway - that's my 2 cents.
 -- Tim