ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
	ksummit-discuss@lists.linuxfoundation.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-discuss] [PATCH v3 1/3] code-of-conduct: Fix the ambiguity about collecting email addresses
Date: Thu, 18 Oct 2018 12:22:25 -0700	[thread overview]
Message-ID: <b9f5376f-d8e8-bfe5-d27e-14c26d4859b8@gmail.com> (raw)
In-Reply-To: <1539874609.2845.5.camel@HansenPartnership.com>

On 10/18/18 07:56, James Bottomley wrote:
> On Wed, 2018-10-17 at 12:53 -0700, Frank Rowand wrote:
>> On 10/17/18 12:08, James Bottomley wrote:
> [...]
>>>> Trying to understand how you are understanding my comment vs what
>>>> I intended to communicate, it seems to me that you are focused on
>>>> the "where allowed" and I am focused on the "which email
>>>> addresses".
>>>>
>>>> More clear?  Or am I still not communicating well enough?
>>>
>>> I think the crux of the disagreement is that you think the carve
>>> out equates to a permission which is not specific enough and I
>>> think it
>>
>> Nope.  That is a big place where I was not transferring my thoughts
>> to clear communication.  I agree that what I wrote should have been
>> written in terms of carve out instead of permission.
>>
>>
>>> doesn't equate to a permission at all, which is why there's no need
>>> to make it more explicit.  Is that a fair characterisation?
>>
>> Nope.  My concern is "which email addresses".
> 
> The idea here was because it's a carve out that doesn't give permission
> and because the permission is ruled by the project contribution
> documents, the carve out should be broad enough to cover anything they
> might say hence "email addresses not ordinarily collected by the
> project" are still included as unacceptable behaviour.
> 
> Perhaps if you propose the wording you'd like to see it would help
> because there still looks to be some subtlety I'm not getting.


>From the beginning of the thread:

  > @@ -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


Alternative (and I'm sure someone else can probably clean this up a little bit):

+ address that has been provided in a public space for the project, without explicit permission


See you in Edinburgh,

-Frank


> 
> James
> 
> 
> 
> 

  reply	other threads:[~2018-10-18 19:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16 14:57 [Ksummit-discuss] [PATCH v3 0/3] code of conduct fixes James Bottomley
2018-10-16 14:58 ` [Ksummit-discuss] [PATCH v3 1/3] code-of-conduct: Fix the ambiguity about collecting email addresses James Bottomley
2018-10-17  2:10   ` Frank Rowand
2018-10-17  2:41     ` James Bottomley
2018-10-17 18:49       ` Frank Rowand
2018-10-17 19:07         ` Randy Dunlap
2018-10-17 19:08         ` James Bottomley
2018-10-17 19:53           ` Frank Rowand
2018-10-18 14:56             ` James Bottomley
2018-10-18 19:22               ` Frank Rowand [this message]
2018-10-18 19:49                 ` Tim.Bird
2018-10-18 19:57                   ` James Bottomley
2018-10-18 23:07                     ` Frank Rowand
2018-10-17 19:26         ` Alexandre Belloni
2018-10-16 14:59 ` [Ksummit-discuss] [PATCH v3 2/3] code-of-conduct: Strip the enforcement paragraph pending community discussion James Bottomley
2018-10-16 15:00 ` [Ksummit-discuss] [PATCH v3 3/3] code-of-conduct: Add back the TAB as the central reporting point James Bottomley
2018-10-17 15:32   ` Shuah Khan

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=b9f5376f-d8e8-bfe5-d27e-14c26d4859b8@gmail.com \
    --to=frowand.list@gmail.com \
    --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