From: Shuah Khan <skhan@linuxfoundation.org>
To: Dave Hansen <dave.hansen@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: Mon, 22 Apr 2024 03:45:51 -0600 [thread overview]
Message-ID: <b94cf7b6-de26-4db1-92d6-2552ff9bb52d@linuxfoundation.org> (raw)
In-Reply-To: <49be8213-361e-41cb-af8d-cb4942064b95@intel.com>
On 4/17/24 13:32, Dave Hansen wrote:
> On 4/12/24 08:38, Shuah Khan wrote:
>> The result of the investigation:
>> - Education and coaching clarifying the role of Code of Conduct
>> conduct on conversations that don't go against the CoC.
>> - Education and coaching the individuals on the impact of making
>> unprofessional comments which could be misunderstood leading
>> to negative impressions about the community.
>>
>> The reports were about the offhand comments made while rejecting
>> the code which are not violations of the Code of Conduct.
>>
>> Unacceptable behavior or comments on a private invitee only chat
>> channel: 1
>> - Education and coaching clarifying the role of Code of Conduct
>> conduct on conversations that occur on a private chat channel.
>
> Looks good to me as well.
>
> Is there any opportunity here to improve the documentation? Or is this
> education and coaching generally for cases where the existing docs
> weren't being read in the first place?
It is the case of not reading the existing documents and/or misunderstanding
the role of CoC. This is similar to what we see in patch submissions - even
with documentation on how to submit patches, we still see it not followed.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-04-22 9:45 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
2024-04-17 19:32 ` Dave Hansen
2024-04-22 9:45 ` Shuah Khan [this message]
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=b94cf7b6-de26-4db1-92d6-2552ff9bb52d@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=conduct@kernel.org \
--cc=dave.hansen@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.