From: Jason Cooper <jason@lakedaemon.net>
To: Chris Mason <clm@fb.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Tech Board Discuss
<Tech-board-discuss@lists.linux-foundation.org>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] better hot-topic discussion processes was: Re: TAB non-nomination
Date: Sat, 10 Nov 2018 21:55:37 +0000 [thread overview]
Message-ID: <20181110215537.GC9256@io.lakedaemon.net> (raw)
In-Reply-To: <2C4B571B-A940-4B41-90C0-D1CE277EAAF0@fb.com>
Hi Chris,
On Sat, Nov 10, 2018 at 07:26:55PM +0000, Chris Mason wrote:
> On 9 Nov 2018, at 12:17, Jason Cooper wrote:
> > On Fri, Nov 09, 2018 at 02:03:05PM -0500, Theodore Y. Ts'o wrote:
> >> So what was done with the update to the CoC was that a proposed set of
> >> changes was sent out to the top 200 or so contributors to the kernel,
> >> by git statistics over the past year, asking for their comments and
> >> their sign-offs. So there *was* community input, and that input did
> >> result in changes to the CoC update.
> >>
> >> Could there be a better process? I think we're all open to input. If
> >> someone would like to suggest a better way to handle things, that
> >> would be great. I will disclose upfront, though, that I will have to
> >> politely disagree with the proposition that completely free and open
> >> discussion is always the magic bullet solution.
> >
> > Ok, I'll take a stab at that. :)
> >
> > I'll make the assumption that there was nothing said in the "invited"
> > discussion that the speaker would object to being a matter of public
> > record.
>
> I'm snipping the rest because you lost me right here ;)
In light of your other, slightly more verbose email (venue for objectors
to speak freely), I agree. I was not aware that was a primary reason
for the "community, but non-public" discussion.
That is a tremendously valuable aspect of the decision, that I'd not
seen conveyed clearly until your email. Thanks for sharing it.
thx,
Jason.
next prev parent reply other threads:[~2018-11-10 21:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 0:04 [Ksummit-discuss] " James Bottomley
2018-11-09 0:29 ` [Ksummit-discuss] [Tech-board-discuss] " Steven Rostedt
2018-11-09 3:30 ` [Ksummit-discuss] " Chris Mason
2018-11-09 17:52 ` Shuah Khan
2018-11-09 19:03 ` Theodore Y. Ts'o
2018-11-09 19:23 ` Joe Perches
2018-11-10 21:21 ` Theodore Y. Ts'o
2018-11-10 21:47 ` Joe Perches
2018-11-12 17:15 ` James Morris
2018-11-09 20:17 ` [Ksummit-discuss] better hot-topic discussion processes was: " Jason Cooper
2018-11-10 19:26 ` Chris Mason
2018-11-10 21:55 ` Jason Cooper [this message]
2018-11-14 18:25 ` [Ksummit-discuss] " Geert Uytterhoeven
2018-11-09 19:54 ` [Ksummit-discuss] [Tech-board-discuss] " Frank Rowand
2018-11-10 19:15 ` Chris Mason
2018-11-10 21:59 ` Jason Cooper
2018-11-11 3:18 ` Frank Rowand
2018-11-11 5:57 ` Theodore Y. Ts'o
2018-11-12 4:44 ` NeilBrown
2018-11-12 4:54 ` NeilBrown
2018-11-12 17:00 ` Steven Rostedt
2018-11-13 16:49 ` Jani Nikula
2018-11-13 19:59 ` Laurent Pinchart
2018-11-14 17:28 ` Mark Brown
2018-11-09 17:19 ` [Ksummit-discuss] " Stephen Hemminger
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=20181110215537.GC9256@io.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Tech-board-discuss@lists.linux-foundation.org \
--cc=clm@fb.com \
--cc=ksummit-discuss@lists.linuxfoundation.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