From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Shuah Khan <shuah@kernel.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Tech Board Discuss
<Tech-board-discuss@lists.linux-foundation.org>
Subject: Re: [Tech-board-discuss] [Ksummit-discuss] TAB non-nomination
Date: Fri, 9 Nov 2018 14:03:05 -0500 [thread overview]
Message-ID: <20181109190305.GD21078@thunk.org> (raw)
In-Reply-To: <41b03a5b-1af4-0a87-2736-016f79d4d1ca@kernel.org>
On Fri, Nov 09, 2018 at 10:52:55AM -0700, Shuah Khan wrote:
> >> The third mistake was dumping the fully formed CoC and a later update
> >> into the tree with little to no community input
>
> It is unfortunate it had to start that way. I also understand at times it
> might be necessary to do so based on my experience with the Linux Kernel
> Community Enforcement Statement process. What should TAB do as a body if
> it needs to take action without an option to initiate an open discussion?
As Chris mentioned, there was a large amount of community input on the
update. It just didn't happen in an open fashion. One of the
challenges with e-mail discussion is that it can end up get dominated
by a small number of people who send a large number of messages. In
an in-person meeting, a good moderator can say, "Alexis, you've been
talking a lot; perhaps we should hear from some other people who have
been quiet. Drew, what do you think?" It's a lot harder to do this
on a mailing list.
The second challenge is that we were getting trolled by people who
were *not* members of the kernel development community. I was able to
track down one such troll to their social media presence on gab.ai.
(Yeah, that same lovely "free speech absolutists' site, for when
Twitter considers you too toxic" which got deplatformed after the
shooting at the Tree of Life Synagogue in Pittsburgh.)
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.
Regards,
- Ted
next prev parent reply other threads:[~2018-11-09 19:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 0:04 [Tech-board-discuss] TAB non-nomination James Bottomley
2018-11-09 0:29 ` Steven Rostedt
2018-11-09 3:30 ` [Tech-board-discuss] [Ksummit-discuss] " Chris Mason
2018-11-09 17:52 ` Shuah Khan
2018-11-09 19:03 ` Theodore Y. Ts'o [this message]
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 ` [Tech-board-discuss] better hot-topic discussion processes was: " Jason Cooper
2018-11-10 19:26 ` [Tech-board-discuss] [Ksummit-discuss] " Chris Mason
2018-11-10 21:55 ` Jason Cooper
2018-11-14 18:25 ` [Tech-board-discuss] [Ksummit-discuss] " Geert Uytterhoeven
2018-11-09 19:54 ` 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 ` 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=20181109190305.GD21078@thunk.org \
--to=tytso@mit.edu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Tech-board-discuss@lists.linux-foundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=shuah@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