All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [PATCH v2 1/3] code-of-conduct: Fix the ambiguity about collecting email addresses
Date: Mon, 15 Oct 2018 13:58:13 -0700	[thread overview]
Message-ID: <CAGXu5jLmpB1t1DFNeUj3chGv6EiEuNHXnFXFshEKAqPokA5X9w@mail.gmail.com> (raw)
In-Reply-To: <1539202115.12644.9.camel@HansenPartnership.com>

On Wed, Oct 10, 2018 at 1:08 PM, James Bottomley
<James.Bottomley@hansenpartnership.com> 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.
>
> Fixes: 8a104f8b5867c682 ("Code of Conduct: Let's revamp it.")
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Acked-by: Shuah Khan <shuah@kernel.org>
> Acked-by: Guenter Roeck <linux@roeck-us.net>
> Reviewed-by: Alan Cox <alan@llwyncelyn.cymru>
> Reviewed-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>

Acked-by: Kees Cook <keescook@chromium.org>

-Kees

> ---
>  Documentation/process/code-of-conduct.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/process/code-of-conduct.rst b/Documentation/process/code-of-conduct.rst
> index ab7c24b5478c..aa40e34e7785 100644
> --- a/Documentation/process/code-of-conduct.rst
> +++ b/Documentation/process/code-of-conduct.rst
> @@ -31,7 +31,7 @@ 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 not ordinarily collected by the project, without explicit permission
>  * Other conduct which could reasonably be considered inappropriate in a
>    professional setting
>
> --
> 2.13.7
>



-- 
Kees Cook
Pixel Security

WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] code-of-conduct: Fix the ambiguity about collecting email addresses
Date: Mon, 15 Oct 2018 13:58:13 -0700	[thread overview]
Message-ID: <CAGXu5jLmpB1t1DFNeUj3chGv6EiEuNHXnFXFshEKAqPokA5X9w@mail.gmail.com> (raw)
In-Reply-To: <1539202115.12644.9.camel@HansenPartnership.com>

On Wed, Oct 10, 2018 at 1:08 PM, James Bottomley
<James.Bottomley@hansenpartnership.com> 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.
>
> Fixes: 8a104f8b5867c682 ("Code of Conduct: Let's revamp it.")
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Acked-by: Shuah Khan <shuah@kernel.org>
> Acked-by: Guenter Roeck <linux@roeck-us.net>
> Reviewed-by: Alan Cox <alan@llwyncelyn.cymru>
> Reviewed-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>

Acked-by: Kees Cook <keescook@chromium.org>

-Kees

> ---
>  Documentation/process/code-of-conduct.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/process/code-of-conduct.rst b/Documentation/process/code-of-conduct.rst
> index ab7c24b5478c..aa40e34e7785 100644
> --- a/Documentation/process/code-of-conduct.rst
> +++ b/Documentation/process/code-of-conduct.rst
> @@ -31,7 +31,7 @@ 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 not ordinarily collected by the project, without explicit permission
>  * Other conduct which could reasonably be considered inappropriate in a
>    professional setting
>
> --
> 2.13.7
>



-- 
Kees Cook
Pixel Security

  parent reply	other threads:[~2018-10-15 20:58 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 20:07 [Ksummit-discuss] [PATCH v2 0/3] code of conduct fixes James Bottomley
2018-10-10 20:07 ` James Bottomley
2018-10-10 20:08 ` [Ksummit-discuss] [PATCH v2 1/3] code-of-conduct: Fix the ambiguity about collecting email addresses James Bottomley
2018-10-10 20:08   ` James Bottomley
2018-10-10 22:17   ` [Ksummit-discuss] " Eric W. Biederman
2018-10-10 22:17     ` Eric W. Biederman
2018-10-11  2:33   ` Mauro Carvalho Chehab
2018-10-11  2:33     ` Mauro Carvalho Chehab
2018-10-15 20:58   ` Kees Cook [this message]
2018-10-15 20:58     ` Kees Cook
2018-10-10 20:09 ` [Ksummit-discuss] [PATCH v2 2/3] code-of-conduct: Strip the enforcement paragraph pending community discussion James Bottomley
2018-10-10 20:09   ` James Bottomley
2018-10-10 21:04   ` [Ksummit-discuss] " Luck, Tony
2018-10-10 21:04     ` Luck, Tony
2018-10-10 21:19     ` James Bottomley
2018-10-10 21:19       ` James Bottomley
2018-10-10 21:28       ` Luck, Tony
2018-10-10 21:28         ` Luck, Tony
2018-10-15 21:02     ` Kees Cook
2018-10-15 21:02       ` Kees Cook
2018-10-11  2:37   ` Mauro Carvalho Chehab
2018-10-11  2:37     ` Mauro Carvalho Chehab
2018-10-10 20:10 ` [Ksummit-discuss] [PATCH v2 3/3] code-of-conduct: Add back the TAB as the central reporting point James Bottomley
2018-10-10 20:10   ` James Bottomley
2018-10-10 20:13   ` [Ksummit-discuss] " Alan Cox
2018-10-10 20:13     ` Alan Cox
2018-10-11  2:30     ` [Ksummit-discuss] " Mauro Carvalho Chehab
2018-10-11  6:50     ` Geert Uytterhoeven
2018-10-11  6:50       ` Geert Uytterhoeven
2018-10-10 21:04   ` [Ksummit-discuss] " Konrad Rzeszutek Wilk
2018-10-10 21:04     ` Konrad Rzeszutek Wilk
2018-10-10 23:23 ` [Ksummit-discuss] [PATCH v2 0/3] code of conduct fixes Eric W. Biederman
2018-10-10 23:23   ` Eric W. Biederman
2018-10-10 23:41   ` Al Viro
2018-10-10 23:41     ` Al Viro
2018-10-11  0:00   ` James Bottomley
2018-10-11  3:11     ` Mauro Carvalho Chehab
2018-10-11  3:11       ` Mauro Carvalho Chehab
2018-10-11 10:43   ` Rainer Fiebig
2018-10-11  6:39 ` Tomi Valkeinen

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=CAGXu5jLmpB1t1DFNeUj3chGv6EiEuNHXnFXFshEKAqPokA5X9w@mail.gmail.com \
    --to=keescook@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.