From: Steven Rostedt <rostedt@goodmis.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: "tech-board-discuss@lists.linuxfoundation.org"
<tech-board-discuss@lists.linuxfoundation.org>,
"conduct@kernel.org" <conduct@kernel.org>
Subject: Re: Linux Kernel Code of Conduct Committee: March 31, 2024
Date: Sun, 28 Apr 2024 16:00:23 -0400 [thread overview]
Message-ID: <20240428160023.1fa830ec@rorschach.local.home> (raw)
In-Reply-To: <97f44075-8bef-479d-bebb-f44c1a5886df@linuxfoundation.org>
On Fri, 12 Apr 2024 09:38:27 -0600
Shuah Khan <skhan@linuxfoundation.org> wrote:
> Dear TAB members,
>
> Please review this Code of Conduct Report for October 1, 2023 through
> March 31, 2024 and give us feedback.
>
> --------------------------------------------------------------------
>
> Linux Kernel Code of Conduct Committee: March 31, 2024
>
> In the period of October 1, 2023 through March 31, 2024, the Code of
> Conduct Committee received the following reports:
>
> Unprofessional behavior or comments in email: 2
>
> 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.
>
> We would like to thank the Linux kernel community members who have
> supported the adoption of the Code of Conduct and who continue to
> uphold the professional standards of our community. If you have
> questions about this report, please write to <conduct@kernel.org>.
>
> --------------------------------------------------------------------
>
[ Coming back from my travels in Japan and catching up on email
(6 hour layover in Detroit!) ]
LGTM.
-- Steve
next prev parent reply other threads:[~2024-04-28 20:00 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
2024-04-22 15:25 ` Theodore Ts'o
2024-04-28 20:00 ` Steven Rostedt [this message]
-- 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=20240428160023.1fa830ec@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=conduct@kernel.org \
--cc=skhan@linuxfoundation.org \
--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.