From: NeilBrown <neilb@suse.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
Frank Rowand <frowand.list@gmail.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] [Tech-board-discuss] TAB non-nomination
Date: Mon, 12 Nov 2018 15:44:18 +1100 [thread overview]
Message-ID: <87o9auvra5.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20181111055728.GC12818@thunk.org>
[-- Attachment #1: Type: text/plain, Size: 2095 bytes --]
On Sun, Nov 11 2018, Theodore Y. Ts'o wrote:
> On Sat, Nov 10, 2018 at 07:18:00PM -0800, Frank Rowand wrote:
>> OK. So the update was done in an opaque closed fashion, which involved
>> soliciting input from some unknown fraction of the community. Do I
>> understand that correctly?
>>
>> And I think it would be fair to say that the people who created the
>> update were probably aware of the comments of a much larger group of
>> people who had participated in the threads on various email lists,
>> and also I suspect the comments threads on the related lwn articles.
>> So likely also based on input from a (probably) larger fraction of
>> the community who had been willing to publicly comment.
>>
>> So based on community input, but the document was not reviewed by the
>> broader community, or accepted by the broader community.
>
> "Community" is a very slippery term. I will note that there were
> *many* people who were participating on the threads, sometimes in very
> non-constructive or in a downright toxic fashion, who had zero commits
> in recent years. In some cases, it was zero commits, *ever*. I
> recall doing the research on one prolific author and found that while
> he did contribute the kernel, it was 3 or 4 commits... ~5 years
> ago... to a driver.
>
> And then there was one person who admitted that while he was just a
> user, he insisted he had a right to weigh in the issue. They
> certainly have the right to have that belief, of course. Whether or
> not maintainers are obliged to cater to people with those beliefs is a
> very different question, however.
>
> There seems to be an assumption that a open, public discussion will
> always give you the best review.
Maybe not, but it does help create a sense of community. It encourages
people to feel valued and included.
The new CoC suggests that our standards include
* Focusing on what is best for the community
Is having a perfect CoC best for the community? Or is having an open
process best, even when it produces a suboptimal result?
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-11-12 4:44 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
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 [this message]
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=87o9auvra5.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Tech-board-discuss@lists.linux-foundation.org \
--cc=frowand.list@gmail.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tytso@mit.edu \
/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