public inbox for tech-board-discuss@lists.linux.dev
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Frank Rowand <frowand.list@gmail.com>
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: Sun, 11 Nov 2018 00:57:28 -0500	[thread overview]
Message-ID: <20181111055728.GC12818@thunk.org> (raw)
In-Reply-To: <3b861369-0fc0-c746-4b1b-047ce903cc30@gmail.com>

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.  I don't think that's necessarily
true.  It can often give you a very biased sample from the poeple who
are most stridently on one side of the debate or the other, as well as
being biased towards those who believe in the "last post wins" style
of debate, since they end up speaking most loudly and posting most
frequently and most aggressively.

I found it very interesting that by explicitly asking the top ranked
developers by git statistics for comments and for their sign-off on
the various update patches, we got a much broader read on what people
thought, and received some very thoughtful comments --- from people
who had *not* engaged on the public threads.

At this point, Linus has indicated that he would prefer that we not
try to tweak the CoC any further, and let's see how it works out in
practice.  If new developers continue to report that they feel more
welcome, and we get more news reports like this:

https://www.zdnet.com/article/a-kinder-gentler-linus-torvalds-and-linux-4-20/

... and no one is getting kicked out of Linux development for being
politically incorrect, and the quality and quantity of kernel code
continues to increase, it'll all be good and we can spend most of our
time worrying about technical rather than political issues.

     	      	    	      	     	  - Ted

  reply	other threads:[~2018-11-11  5:57 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
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 [this message]
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=20181111055728.GC12818@thunk.org \
    --to=tytso@mit.edu \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Tech-board-discuss@lists.linux-foundation.org \
    --cc=frowand.list@gmail.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