From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 2D64DF04 for ; Wed, 19 Sep 2018 23:29:00 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id F19C867F for ; Wed, 19 Sep 2018 23:28:58 +0000 (UTC) Date: Wed, 19 Sep 2018 20:28:52 -0300 From: Mauro Carvalho Chehab To: "Luck, Tony" Message-ID: <20180919202852.0da5c649@coco.lan> In-Reply-To: <20180919201015.GA31523@agluck-desk> References: <1537279328.3424.6.camel@HansenPartnership.com> <20180918162948.769dda1d@coco.lan> <1537356482.4640.7.camel@HansenPartnership.com> <20180919083749.49268562@coco.lan> <20180919090332.723c1b75@coco.lan> <1537366581.6816.1.camel@HansenPartnership.com> <20180919165552.0f30bbef@coco.lan> <20180919201015.GA31523@agluck-desk> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: James Bottomley , ksummit Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC FOR KS] CoC and Linus position (perhaps undocumented/closed/limited/invite session) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Em Wed, 19 Sep 2018 13:10:15 -0700 "Luck, Tony" 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. > >=20 > > The thing is that, when it uses the commas there: > >=20 > > "private information, such as a physical or electronic address,"=20 > >=20 > > The commas actually defines what "private information" is. Even if > > this would be changed by "foo information", what we have here is actual= ly two > > English sentences that were merged together: > >=20 > > First sentence: > > "Private information, such as a physical or electronic address." > >=20 > > Second sentence: > > "Publishing others=E2=80=99 private information without explicit permi= ssion" > >=20 > > See, replace it by foo at the original text: > > "Publishing others=E2=80=99 *foo* information, such as a physical=20 > > or electronic address, without explicit permission" > >=20 > > You'll see that "*foo* information" becomes defined. =20 >=20 > So perhaps we can move on to discussing a patch to fix it? >=20 >=20 > diff --git a/Documentation/process/code-of-conduct.rst b/Documentation/pr= ocess/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 inc= lude: > * Trolling, insulting/derogatory comments, and personal or political att= acks > * Public or private harassment > * Publishing others=E2=80=99 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 > =20 > +[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. > =20 > Our Responsibilities > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Reviewed-by: Mauro Carvalho Chehab Thanks, Mauro