ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
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: Wed, 14 Nov 2018 09:28:55 -0800	[thread overview]
Message-ID: <20181114172855.GW2089@sirena.org.uk> (raw)
In-Reply-To: <20181111055728.GC12818@thunk.org>

[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]

On Sun, Nov 11, 2018 at 12:57:28AM -0500, Theodore Y. Ts'o wrote:

> 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.

One thing that other organisations that do this sort of consultation
process (which is very good and useful) do which didn't seem to happen
here is that they announce that this is going on.  This is useful
because it helps people know what's going on and can help make the
public discussion a bit more useful as a result.  If, as is common,
there's also some way for people to push in comments those can turn up
useful feedback that people you wouldn't have thought to ask aren't
comfortable providing in public though you'll also tend to get a lot of
noise in there as well if it's a contentious area so that's hard work.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2018-11-14 17:28 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
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 [this message]
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=20181114172855.GW2089@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Tech-board-discuss@lists.linux-foundation.org \
    --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