All of lore.kernel.org
 help / color / mirror / Atom feed
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] [Tech-board-discuss]  TAB non-nomination
Date: Sat, 10 Nov 2018 21:59:32 +0000	[thread overview]
Message-ID: <20181110215932.GD9256@io.lakedaemon.net> (raw)
In-Reply-To: <0F1E6845-9F6D-46E2-BB52-8B0C2D8103C6@fb.com>

Hi Chris,

On Sat, Nov 10, 2018 at 07:15:16PM +0000, Chris Mason wrote:
...
> Ted's earlier reply has a good summary, but the part I want to underline 
> is that we sought out people who strongly disagreed with us, and we did 
> our best to understand their concerns.  It was important to me that we 
> give people a private channel to express themselves, especially 
> considering that the topic at hand was behavior on public lists.
> 
> It was a tradeoff, but I was really happy with the number of people who 
> participated who might otherwise have stayed out of the discussion 
> completely.

This is the most concise and clear explanation for the path taken.
Thanks for sharing it with everyone.

thx,

Jason.

WARNING: multiple messages have this Message-ID (diff)
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: [Tech-board-discuss] [Ksummit-discuss]   TAB non-nomination
Date: Sat, 10 Nov 2018 21:59:32 +0000	[thread overview]
Message-ID: <20181110215932.GD9256@io.lakedaemon.net> (raw)
In-Reply-To: <0F1E6845-9F6D-46E2-BB52-8B0C2D8103C6@fb.com>

Hi Chris,

On Sat, Nov 10, 2018 at 07:15:16PM +0000, Chris Mason wrote:
...
> Ted's earlier reply has a good summary, but the part I want to underline 
> is that we sought out people who strongly disagreed with us, and we did 
> our best to understand their concerns.  It was important to me that we 
> give people a private channel to express themselves, especially 
> considering that the topic at hand was behavior on public lists.
> 
> It was a tradeoff, but I was really happy with the number of people who 
> participated who might otherwise have stayed out of the discussion 
> completely.

This is the most concise and clear explanation for the path taken.
Thanks for sharing it with everyone.

thx,

Jason.

  reply	other threads:[~2018-11-10 22:15 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09  0:04 [Ksummit-discuss] TAB non-nomination James Bottomley
2018-11-09  0:04 ` [Tech-board-discuss] " James Bottomley
2018-11-09  0:29 ` [Ksummit-discuss] " Steven Rostedt
2018-11-09  0:29   ` Steven Rostedt
2018-11-09  3:30 ` [Ksummit-discuss] " Chris Mason
2018-11-09  3:30   ` [Tech-board-discuss] " Chris Mason
2018-11-09 17:52   ` Shuah Khan
2018-11-09 17:52     ` [Tech-board-discuss] " Shuah Khan
2018-11-09 19:03     ` Theodore Y. Ts'o
2018-11-09 19:03       ` [Tech-board-discuss] " Theodore Y. Ts'o
2018-11-09 19:23       ` Joe Perches
2018-11-09 19:23         ` [Tech-board-discuss] " Joe Perches
2018-11-10 21:21         ` Theodore Y. Ts'o
2018-11-10 21:21           ` [Tech-board-discuss] " Theodore Y. Ts'o
2018-11-10 21:47           ` Joe Perches
2018-11-10 21:47             ` [Tech-board-discuss] " Joe Perches
2018-11-12 17:15           ` James Morris
2018-11-12 17:15             ` [Tech-board-discuss] " James Morris
2018-11-09 20:17       ` [Ksummit-discuss] better hot-topic discussion processes was: " Jason Cooper
2018-11-09 20:17         ` [Tech-board-discuss] " Jason Cooper
2018-11-10 19:26         ` [Ksummit-discuss] " Chris Mason
2018-11-10 19:26           ` [Tech-board-discuss] " Chris Mason
2018-11-10 21:55           ` Jason Cooper
2018-11-10 21:55             ` [Tech-board-discuss] " Jason Cooper
2018-11-14 18:25       ` [Ksummit-discuss] " Geert Uytterhoeven
2018-11-14 18:25         ` [Tech-board-discuss] " Geert Uytterhoeven
2018-11-09 19:54   ` [Ksummit-discuss] [Tech-board-discuss] " Frank Rowand
2018-11-09 19:54     ` [Tech-board-discuss] [Ksummit-discuss] " Frank Rowand
2018-11-10 19:15     ` [Ksummit-discuss] [Tech-board-discuss] " Chris Mason
2018-11-10 19:15       ` [Tech-board-discuss] [Ksummit-discuss] " Chris Mason
2018-11-10 21:59       ` Jason Cooper [this message]
2018-11-10 21:59         ` Jason Cooper
2018-11-11  3:18       ` [Ksummit-discuss] [Tech-board-discuss] " Frank Rowand
2018-11-11  3:18         ` [Tech-board-discuss] [Ksummit-discuss] " Frank Rowand
2018-11-11  5:57         ` [Ksummit-discuss] [Tech-board-discuss] " Theodore Y. Ts'o
2018-11-11  5:57           ` [Tech-board-discuss] [Ksummit-discuss] " Theodore Y. Ts'o
2018-11-12  4:44           ` [Ksummit-discuss] [Tech-board-discuss] " NeilBrown
2018-11-12  4:44             ` [Tech-board-discuss] [Ksummit-discuss] " NeilBrown
2018-11-12  4:54           ` [Ksummit-discuss] [Tech-board-discuss] " NeilBrown
2018-11-12  4:54             ` [Tech-board-discuss] [Ksummit-discuss] " NeilBrown
2018-11-12 17:00             ` [Ksummit-discuss] [Tech-board-discuss] " Steven Rostedt
2018-11-12 17:00               ` [Tech-board-discuss] [Ksummit-discuss] " Steven Rostedt
2018-11-13 16:49           ` [Ksummit-discuss] [Tech-board-discuss] " Jani Nikula
2018-11-13 16:49             ` [Tech-board-discuss] [Ksummit-discuss] " Jani Nikula
2018-11-13 19:59             ` [Ksummit-discuss] [Tech-board-discuss] " Laurent Pinchart
2018-11-13 19:59               ` [Tech-board-discuss] [Ksummit-discuss] " Laurent Pinchart
2018-11-14 17:28           ` [Ksummit-discuss] [Tech-board-discuss] " Mark Brown
2018-11-14 17:28             ` [Tech-board-discuss] [Ksummit-discuss] " Mark Brown
2018-11-09 17:19 ` Stephen Hemminger
2018-11-09 17:19   ` [Tech-board-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=20181110215932.GD9256@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.