From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC FOR KS] CoC and Linus position (perhaps undocumented/closed/limited/invite session)
Date: Wed, 19 Sep 2018 02:38:18 +0300 [thread overview]
Message-ID: <7909721.24ppt1u8vO@avalon> (raw)
In-Reply-To: <20180918190618.6be95e7b@gandalf.local.home>
On Wednesday, 19 September 2018 02:06:18 EEST Steven Rostedt wrote:
> On Tue, 18 Sep 2018 12:36:45 -0700 Josh Triplett wrote:
> > > 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.
> >
> > (Publishing someone's private, otherwise-unpublished email address in an
> > Acked-by, on the other hand, *could* be problematic. Don't do that.)
>
> And this has been my work flow all along. I'm very conscience of taking
> someone's email and publishing it in a "Reported-by". I will first send
> an email to the submitter and ask if it is OK to include them if they
> sent me the bug report privately.
>
> But yes, if someone sends me a report and Cc's LKML, I will add the
> Reported-by with the email address that they used to a public address
> without any confirmation.
Taking a step back, I'd like to clarify the intent of this specific provision
before discussing its working or any FAQ entry that we believe is needed.
As I understand it, the intent is to avoid individuals being put under the
spotlight without consent, with the risks of harassment that could follow (or,
probably usual in the problematic cases, with the disclosure already being
part of a harassment campaign).
If that assumption is correct, I believe we could clarify the intent by
stating that (probably reworded by a better English speaker than me) is
excluded from private information in the context of a public communication any
information already posted to public channels in the same context (the context
is important here, as if someone digs up messages I posted, let's say on
health-related public forums, with my name hidden but associated with the same
e-mail address, those would still be private information).
Additionally, and this applies more broadly, I believe it would be useful to
clearly state that accidental disclosure of private information that could
reasonably not be interpreted as private by the discloser will not result in
immediate retaliation on the first occurrence. The goal of the code of
conduct, as I interpret it, is to define the generally accepted an unaccepted
behaviour, not to be used as an excuse to punish anyone.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2018-09-18 23:38 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 [this message]
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=7909721.24ppt1u8vO@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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