From: Alexandre Belloni <alexandre.belloni@bootlin.com> To: Frank Rowand <frowand.list@gmail.com> Cc: James Bottomley <James.Bottomley@HansenPartnership.com>, linux-kernel <linux-kernel@vger.kernel.org>, ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [PATCH v3 1/3] code-of-conduct: Fix the ambiguity about collecting email addresses Date: Wed, 17 Oct 2018 21:26:02 +0200 [thread overview] Message-ID: <20181017192602.GA17341@piout.net> (raw) In-Reply-To: <16a20416-0045-dfe6-d937-63f2f0cff269@gmail.com> Hello, On 17/10/2018 11:49:06-0700, Frank Rowand wrote: > Permission vs exclusion is orthogonal to my comments. > > "building linux" is not the patch wording. "ordinarily collected by the > project" is a much broader universe. > > A very simplistic definition of public _could_ be: > > - Visible on a project mail list that any one can subscribe to > - Visible on a project mail list whose archive is available via > the public internet > - Visible on an interactive communication ("chat") platform that > is open to the public internet > - Published on a web page intended for public access (for example > this could cover opt-in conference attendee lists and emails > that conference presenters voluntarily place in their slides). What about properly formatted patches (with From and SoB) sent to the maintainer, without copying any mailing lists? To me, a patch sent to a maintainer is obviously sent for inclusion in the kernel. > - (I am guessing the above covers 97% or more of possible public > sources, but maybe there are some more common sources.) > > I'm sure that the professionals that deal with information privacy > could provide better wording for the above list. I am but an > amateur in that field. > > Anything else collected by the project would not be considered public. > For example, an email address provided in an email sent to me and not > copied to any mail list would not be public. -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Belloni <alexandre.belloni@bootlin.com> To: Frank Rowand <frowand.list@gmail.com> Cc: James Bottomley <James.Bottomley@HansenPartnership.com>, ksummit-discuss@lists.linuxfoundation.org, 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: Wed, 17 Oct 2018 21:26:02 +0200 [thread overview] Message-ID: <20181017192602.GA17341@piout.net> (raw) In-Reply-To: <16a20416-0045-dfe6-d937-63f2f0cff269@gmail.com> Hello, On 17/10/2018 11:49:06-0700, Frank Rowand wrote: > Permission vs exclusion is orthogonal to my comments. > > "building linux" is not the patch wording. "ordinarily collected by the > project" is a much broader universe. > > A very simplistic definition of public _could_ be: > > - Visible on a project mail list that any one can subscribe to > - Visible on a project mail list whose archive is available via > the public internet > - Visible on an interactive communication ("chat") platform that > is open to the public internet > - Published on a web page intended for public access (for example > this could cover opt-in conference attendee lists and emails > that conference presenters voluntarily place in their slides). What about properly formatted patches (with From and SoB) sent to the maintainer, without copying any mailing lists? To me, a patch sent to a maintainer is obviously sent for inclusion in the kernel. > - (I am guessing the above covers 97% or more of possible public > sources, but maybe there are some more common sources.) > > I'm sure that the professionals that deal with information privacy > could provide better wording for the above list. I am but an > amateur in that field. > > Anything else collected by the project would not be considered public. > For example, an email address provided in an email sent to me and not > copied to any mail list would not be public. -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
next prev parent reply other threads:[~2018-10-17 19:26 UTC|newest] Thread overview: 25+ 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:57 ` 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-16 14:58 ` James Bottomley 2018-10-17 2:10 ` [Ksummit-discuss] " 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 2018-10-18 19:22 ` Frank Rowand 2018-10-18 19:49 ` Tim.Bird 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 [this message] 2018-10-17 19:26 ` Alexandre Belloni 2018-10-20 18:11 ` Michael Tirado 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 14:59 ` 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-16 15:00 ` James Bottomley 2018-10-17 15:32 ` [Ksummit-discuss] " 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=20181017192602.GA17341@piout.net \ --to=alexandre.belloni@bootlin.com \ --cc=James.Bottomley@HansenPartnership.com \ --cc=frowand.list@gmail.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: linkBe 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.