ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
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: Tue, 18 Sep 2018 22:52:12 +0200	[thread overview]
Message-ID: <s5h5zz2v88z.wl-tiwai@suse.de> (raw)
In-Reply-To: <20180918165203.69de8cc4@coco.lan>

On Tue, 18 Sep 2018 21:52:03 +0200,
Mauro Carvalho Chehab wrote:
> 
> Em Tue, 18 Sep 2018 12:36:45 -0700
> Josh Triplett <josh@joshtriplett.org> escreveu:
> 
> > On Tue, Sep 18, 2018 at 04:29:48PM -0300, Mauro Carvalho Chehab wrote:
> > > Em Tue, 18 Sep 2018 10:02:08 -0400
> > > James Bottomley <James.Bottomley@HansenPartnership.com> escreveu:
> > >   
> > > > > After the past 2-3 days I get the feeling there are maintainers
> > > > > unsure about how this affects them and I think assuaging those fears
> > > > > might be a good thing.
> > > > >   
> > >   
> > > > From my perspective, which is probably fairly widespread: we're already
> > > > pretty much policing the lists using a set of rules which match fairly
> > > > closely to the new CoC, so there should really be no huge impact.  
> > > 
> > > After carefully reading it a couple of times, I think it has a huge
> > > impact.
> > > 
> > > The more immediate impact is with regards to this wording:
> > > 
> > > 	"Examples of unacceptable behavior by participants include:
> > > 	...
> > > 	* Publishing others’ private information, such as a physical or electronic
> > > 	  address, without explicit permission"
> > > 
> > > When we publish a patch with a Signed-off-by, Reviewed-by, Acked-by,
> > > Requested-by, Suggested-by, etc, we are actually publishing an electronic
> > > address.  
> > 
> > If they've posted public mails from that email address, that isn't
> > "private information" at that point. And in any case someone offering
> > such a tag would constitute permission.
> 
> Good point, but I'm pretty sure it opens multiple interpretation, as
> it explicitly forbids using "electronic address without explicit
> permission".
> 
> > (Publishing someone's private, otherwise-unpublished email address in an
> > Acked-by, on the other hand, *could* be problematic. Don't do that.)
> 
> Well, Requested-by, Suggested-by (and sometimes tested-by) is sometimes
> added by the maintainer (or by the patch writer).

Right, such tags are often used as credits of contributions, too.

Since they are no mandatory stuff like Signed-off-by, we may drop the
address part, though.


Takashi

> > Nonetheless, it probably couldn't hurt to have some notes on this
> > situation somewhere.
> 
> Yes, that's my point: that part of the CoC should explicitly exclude any
> electronic addresses that are used on public community-related channels,
> specially on e-mail [1].
> 
> Thanks,
> Mauro
> 
> [1] While this is not common, I merged in the past some patches whose
> developer included parts of discussions that happened at freenode's
> public IRC channels related to the project.
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

  reply	other threads:[~2018-09-18 20:52 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 [this message]
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
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=s5h5zz2v88z.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=mchehab+samsung@kernel.org \
    /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