From: Shuah Khan <skhan@linuxfoundation.org>
To: Dan Williams <dan.j.williams@intel.com>,
"tech-board-discuss@lists.linuxfoundation.org"
<tech-board-discuss@lists.linuxfoundation.org>
Cc: "conduct@kernel.org" <conduct@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: Linux Kernel Code of Conduct Committee: March 31, 2024
Date: Tue, 23 Apr 2024 02:14:31 -0600 [thread overview]
Message-ID: <5b0d5999-66cb-4792-b70b-47fbec76e8ef@linuxfoundation.org> (raw)
In-Reply-To: <6626b107a3b12_5c7c29451@dwillia2-mobl3.amr.corp.intel.com.notmuch>
On 4/22/24 12:48, Dan Williams wrote:
> Shuah Khan wrote:
>> All,
>>
>> On 4/12/24 09:38, Shuah Khan wrote:
>>> Dear TAB members,
>>>
>>> Please review this Code of Conduct Report for October 1, 2023 through
>>> March 31, 2024 and give us feedback.
>>
>> Please give it a read when you get a chance and give us feedback.
>
> Hi Shuah,
>
> Looks ok to me. This feels like a manageable level of activity, do you
> see any indicators that we as a community need to be more proactive on
> any recurring themes?
Yes it is very manageable. I am not seeing anything that is of a concern.
We have been clarifying maintainer rights and normal review process - but
this is in general addressed quickly once the reporter understands the
process.
As I am writing this, I am thinking we could hold a Ask an Expert session
on CoC at one of the upcoming conferences to be accessible.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-04-23 8:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 15:38 Linux Kernel Code of Conduct Committee: March 31, 2024 Shuah Khan
2024-04-17 17:51 ` Shuah Khan
2024-04-17 19:10 ` Jonathan Corbet
2024-04-22 9:42 ` Shuah Khan
2024-04-23 15:53 ` Jonathan Corbet
2024-04-22 18:48 ` Dan Williams
2024-04-23 8:14 ` Shuah Khan [this message]
2024-04-17 19:32 ` Dave Hansen
2024-04-22 9:45 ` Shuah Khan
2024-04-22 15:25 ` Theodore Ts'o
2024-04-28 20:00 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2024-04-26 14:13 Shuah Khan
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=5b0d5999-66cb-4792-b70b-47fbec76e8ef@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=conduct@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=tech-board-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.