From: Josh Triplett <josh@joshtriplett.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email addresses
Date: Mon, 8 Oct 2018 08:20:44 -0700 [thread overview]
Message-ID: <20181008152043.GA5796@localhost> (raw)
In-Reply-To: <1538861799.4088.6.camel@HansenPartnership.com>
On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> The current code of conduct has an ambiguity in the it considers publishing
> private information such as email addresses unacceptable behaviour. Since
> the Linux kernel collects and publishes email addresses as part of the patch
> process, add an exception clause for email addresses ordinarily collected by
> the project to correct this ambiguity.
Upstream has now adopted a FAQ, which addresses this and many other
questions. See https://www.contributor-covenant.org/faq .
Might I suggest adding that link to the bottom of the document, instead?
(And then, optionally, submitting entries for that FAQ.)
next prev parent reply other threads:[~2018-10-08 15:20 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 21:35 [Ksummit-discuss] [PATCH 0/2] code of conduct fixes James Bottomley
2018-10-06 21:36 ` [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email addresses James Bottomley
2018-10-07 8:25 ` Geert Uytterhoeven
2018-10-07 15:25 ` Shuah Khan
2018-10-07 9:04 ` Daniel Vetter
2018-10-07 9:54 ` Hannes Reinecke
2018-10-07 15:29 ` James Bottomley
2018-10-08 19:49 ` Mauro Carvalho Chehab
2018-10-07 17:53 ` Guenter Roeck
2018-10-07 22:25 ` Dave Airlie
2018-10-07 22:56 ` Al Viro
2018-10-07 23:02 ` Al Viro
2018-10-07 23:37 ` Dave Airlie
2018-10-08 10:14 ` Mark Brown
2018-10-08 19:32 ` Mauro Carvalho Chehab
2018-10-08 17:05 ` Luck, Tony
2018-10-08 14:08 ` James Bottomley
2018-10-10 16:36 ` Pavel Machek
2018-10-08 15:20 ` Josh Triplett [this message]
2018-10-08 15:30 ` James Bottomley
2018-10-08 19:23 ` Mauro Carvalho Chehab
2018-10-08 19:57 ` Josh Triplett
2018-10-09 10:55 ` Mark Brown
[not found] ` <1718828.OxLgMoHbrt@siriux>
2018-10-09 18:56 ` Josh Triplett
2018-10-09 19:38 ` Laurent Pinchart
2018-10-09 19:44 ` James Bottomley
2018-10-08 19:24 ` Mauro Carvalho Chehab
2018-10-10 20:48 ` Frank Rowand
2018-10-06 21:37 ` [Ksummit-discuss] [PATCH 2/2] code-of-conduct: Strip the enforcement paragraph pending community discussion James Bottomley
2018-10-06 21:43 ` Tim.Bird
2018-10-07 3:33 ` James Bottomley
2018-10-08 13:51 ` Tim.Bird
2018-10-08 14:09 ` James Bottomley
2018-10-08 17:58 ` Tim.Bird
2018-10-08 18:11 ` James Bottomley
2018-10-08 18:54 ` Tim.Bird
2018-10-08 15:03 ` jonsmirl
2018-10-08 15:37 ` Alan Cox
2018-10-11 7:42 ` Dan Carpenter
2018-10-07 15:32 ` Shuah Khan
2018-10-07 17:56 ` Guenter Roeck
2018-10-07 19:51 ` Geert Uytterhoeven
2018-10-08 18:15 ` Chris Mason
2018-10-08 19:04 ` Josh Triplett
2018-10-08 20:23 ` Mauro Carvalho Chehab
2018-10-10 15:53 ` Alan Cox
2018-10-10 17:19 ` Mauro Carvalho Chehab
2018-10-10 20:09 ` Alan Cox
2018-10-10 20:30 ` Mauro Carvalho Chehab
2018-10-10 20:32 ` Dave Airlie
2018-10-07 17:11 ` [Ksummit-discuss] [PATCH 0/2] code of conduct fixes Daniel Vetter
2018-10-07 17:40 ` James Bottomley
2018-10-07 17:50 ` jonsmirl
2018-10-07 17:52 ` Daniel Vetter
2018-10-10 16:12 ` Pavel Machek
2018-10-10 16:25 ` Randy Dunlap
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=20181008152043.GA5796@localhost \
--to=josh@joshtriplett.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.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