From: Frank Rowand <frowand.list@gmail.com>
To: Chris Mason <clm@fb.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: 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: Fri, 9 Nov 2018 11:54:31 -0800 [thread overview]
Message-ID: <c6a1629f-df14-6e02-c995-f99a1f691c6a@gmail.com> (raw)
In-Reply-To: <35402D8E-0294-4E34-BE8B-22BCBC20BF66@fb.com>
On 11/8/18 7:30 PM, Chris Mason wrote:
> On 8 Nov 2018, at 16:04, James Bottomley wrote:
>>
>> Hind sight, though is always perfect. At the time, as a TAB member,
>> all you saw was a panic driven by both Linus and the Linux Foundation
>> that we needed an updated Kernel CoC ASAP, like today.
>
> I think panic is the wrong word to attach to Linus' response, especially
> around the code of conduct.
>
>>
>> The second mistake was picking the wrong CoC. [ ... ]
>>
>> The third mistake was dumping the fully formed CoC and a later update
>> into the tree with little to no community input
>
> The update was entirely based on community input.
I am going to try to parse that sentence very carefully and narrowly.
If you are saying that the update (that is, code-of-conduct-interpretation.rst)
then I would agree that the document appears to have been created
based on community input. But that is merely a conjecture on my part
since the document was created in a small closed group.
If you are saying that the creation of code-of-conduct-interpretation.rst
was done in a process that was open and visible to the community, then
I would disagree. I don't know if this is what you meant to convey,
but it is very easy to interpret the sentence in this way.
-Frank
>> which has generated a
>> lot of obvious anger within our community itself.
>
> It's absolutely true that some members of the community were upset.
>
> We'll never know if there could have been a better time to make code of
> conduct changes. There are a wide range of deeply held beliefs in this
> area, and every choice would have eventually led to major disagreements.
> But what we do know is that everyone sat down and did their best to
> find compromise. That doesn't mean we found the right compromise for
> every developer, but I still really appreciate how much time and energy
> everyone spent explaining their point of view and looking for common
> ground.
>
>> All I'll say on this
>> is that revisiting the CoC is going to cause another huge cascade of
>> externally driven attacks which I think we'd all rather avoid, so if
>> you're still ticked, then perhaps you should channel that anger and
>> stand for the TAB ...
>>
>
> It's really important the TAB is full of people that care about the
> kernel. Anger about the code of conduct isn't a great qualifier, but
> I'll happily encourage anyone who cares deeply about the kernel
> community, even if they disagree with my opinions about how to best
> support it.
>
> -chris
> _______________________________________________
> Tech-board-discuss mailing list
> Tech-board-discuss@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/tech-board-discuss
>
next prev parent reply other threads:[~2018-11-09 19:54 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 ` Frank Rowand [this message]
2018-11-10 19:15 ` [Ksummit-discuss] [Tech-board-discuss] " 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 ` [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=c6a1629f-df14-6e02-c995-f99a1f691c6a@gmail.com \
--to=frowand.list@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox