ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC FOR KS] CoC and Linus position (perhaps undocumented/closed/limited/invite session)
Date: Wed, 19 Sep 2018 20:28:52 -0300	[thread overview]
Message-ID: <20180919202852.0da5c649@coco.lan> (raw)
In-Reply-To: <20180919201015.GA31523@agluck-desk>

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>


Thanks,
Mauro

  reply	other threads:[~2018-09-19 23:29 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-18  5:55 Dave Airlie
2018-09-18 13:43 ` Steven Rostedt
2018-09-18 14:34   ` Daniel Vetter
2018-09-18 14:58     ` Geert Uytterhoeven
2018-09-20  9:12   ` Rafael J. Wysocki
2018-09-20  9:53     ` Daniel Vetter
2018-09-20 10:05       ` Daniel Vetter
2018-09-20 15:57       ` Mark Brown
2018-09-18 14:02 ` James Bottomley
2018-09-18 14:41   ` Daniel Vetter
2018-09-18 19:29   ` Mauro Carvalho Chehab
2018-09-18 19:36     ` Josh Triplett
2018-09-18 19:52       ` Mauro Carvalho Chehab
2018-09-18 20:52         ` Takashi Iwai
2018-09-18 21:15         ` Josh Triplett
2018-09-18 23:06       ` Steven Rostedt
2018-09-18 23:38         ` Laurent Pinchart
2018-09-18 19:58     ` Arnaldo Carvalho de Melo
2018-09-19 11:28     ` James Bottomley
2018-09-19 11:37       ` Mauro Carvalho Chehab
2018-09-19 12:03         ` Mauro Carvalho Chehab
2018-09-19 14:16           ` James Bottomley
2018-09-19 16:06             ` Mauro Carvalho Chehab
2018-09-19 19:55             ` Mauro Carvalho Chehab
2018-09-19 20:10               ` Luck, Tony
2018-09-19 23:28                 ` Mauro Carvalho Chehab [this message]
2018-09-19 23:45                   ` Tim.Bird
2018-09-19 20:23               ` Dave Airlie
2018-09-20  0:01                 ` Mauro Carvalho Chehab
2018-09-20  0:22                   ` Tim.Bird
2018-09-20  6:33                     ` Jani Nikula
2018-09-20  7:01                       ` Josh Triplett
2018-09-20  7:11                         ` Daniel Vetter
2018-09-20  7:04                       ` David Woodhouse
2018-09-24 13:53                         ` Mel Gorman
2018-09-25  5:45                           ` Leon Romanovsky
2018-09-20 10:19                       ` Laurent Pinchart
2018-09-20 10:23                       ` Mauro Carvalho Chehab
2018-09-20 12:31                         ` Jani Nikula
2018-09-20 13:04                           ` Mauro Carvalho Chehab
2018-09-20 13:49                         ` Tim.Bird
2018-09-20 13:55                           ` Laurent Pinchart
2018-09-20 19:14                             ` Tim.Bird
2018-09-20 19:55                               ` Laurent Pinchart
2018-09-20 20:11                                 ` Dmitry Torokhov
2018-09-20 20:14                                 ` Jonathan Corbet
2018-09-20 20:52                           ` Mauro Carvalho Chehab
2018-09-20  2:44                   ` Joe Perches
2018-09-20 11:11                     ` Laurent Pinchart
2018-09-20 13:35                       ` Joe Perches
2018-09-20  3:38                   ` Stephen Hemminger
2018-09-20 12:28 ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180919202852.0da5c649@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tony.luck@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox