From: Randy Dunlap <rdunlap@infradead.org>
To: Theodore Ts'o <tytso@mit.edu>, Shuah <shuah@kernel.org>
Cc: tech-board-discuss@lists.linux-foundation.org, ksummit@lists.linux.dev
Subject: Re: [Tech-board-discuss] [MAINTAINERS SUMMIT] Maintainers Support Group
Date: Tue, 19 Sep 2023 15:07:27 -0700 [thread overview]
Message-ID: <40750d00-723d-4d6b-a936-dbe8e22889e7@infradead.org> (raw)
In-Reply-To: <ZQoaUy34siNzH1ir@mit.edu>
On 9/19/23 15:01, Theodore Ts'o wrote:
> On Tue, Sep 19, 2023 at 04:39:11PM -0400, Theodore Ts'o wrote:
>> On Tue, Sep 19, 2023 at 10:52:40AM -0600, Shuah wrote:
>>> As a member of the CoC, I respectfully disagree with the statement "but all the
>>> focus has mainly been around telling maintainers how to behave." This impression
>>> might have been the result of one unfortunate incident that took place last year.
>>> is only part of what CoC has been doing.
>>>
>>> A majority of reports are related to incorrect understanding of how the community
>>> works and discusses technical issues. Most of them get resolved without involving
>>> the community. This is behind the scenes silent work CoC does.
>>>
>>> It is unfortunate that CoC is being viewed as a body that is focused on telling
>>> maintainers how to behave. I would encourage to not view CoC work based on one
>>> or two cases that were outliers. CoC worked very hard to resolve them fairly and
>>> that benefited the community as a whole.
>>
>> Shuah, I don't think this is the fault of the CoC. Much of it is in
>> how people interpret the CoC, or think it should be adapted.
>
> I just realized that this statement was a bit ambiguous; in the first
> CoC, I meant the "Code of Conduct Committee". In the second CoC in
> this sentence, I made the "Code of Conduct".
>
> From the context of what you wrote, I *think* you were consistently
> referring to the Code of Conduct Committee, but when I see CoC I tend
> think the actual "Code of Conduct" and not the committee which
> enforces the CoC.
>
> Apologies for any confusion,
Thanks for explaining. I was confused by Shuah's comments (but I
came to the same conclusion that you did).
--
~Randy
next prev parent reply other threads:[~2023-09-19 22:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 16:10 [Tech-board-discuss] [MAINTAINERS SUMMIT] Maintainers Support Group Steven Rostedt
2023-09-19 16:52 ` Shuah
2023-09-19 17:19 ` Steven Rostedt
2023-09-19 17:29 ` Steven Rostedt
2023-09-19 17:54 ` James Bottomley
2023-09-19 21:26 ` Shuah
2023-09-19 20:39 ` Theodore Ts'o
2023-09-19 21:02 ` Steven Rostedt
2023-09-20 12:03 ` Christian Brauner
2023-09-19 22:01 ` Theodore Ts'o
2023-09-19 22:07 ` Randy Dunlap [this message]
2023-09-19 22:40 ` Shuah
2023-09-19 22:32 ` Shuah
2023-09-19 22:53 ` Shuah
[not found] ` <dbeb5ad9-fa6d-4633-a160-6a0f8ed6bd51@acm.org>
2023-09-19 17:21 ` Steven Rostedt
2023-09-19 22:55 ` Shuah
2023-09-19 23:21 ` Steven Rostedt
2023-09-20 7:06 ` Linus Walleij
2023-09-20 19:52 ` Shuah
2023-09-20 22:54 ` Laurent Pinchart
2023-09-21 0:45 ` Shuah
2023-09-21 12:40 ` Linus Walleij
2023-09-21 12:56 ` Laurent Pinchart
2023-09-19 17:48 ` Dave Taht
2023-09-20 15:45 ` Mark Brown
2023-10-05 18:08 ` Jason Gunthorpe
2023-10-06 20:47 ` Linus Walleij
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=40750d00-723d-4d6b-a936-dbe8e22889e7@infradead.org \
--to=rdunlap@infradead.org \
--cc=ksummit@lists.linux.dev \
--cc=shuah@kernel.org \
--cc=tech-board-discuss@lists.linux-foundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).