From: Shuah Khan <skhan@linuxfoundation.org> To: linux-kernel@vger.kernel.org Cc: tech-board-discuss@lists.linuxfoundation.org, "conduct@kernel.org" <conduct@kernel.org> Subject: Linux Kernel Code of Conduct Committee: April 2021 report Date: Tue, 18 May 2021 13:09:29 -0600 [thread overview] Message-ID: <448b06e4-41fc-26df-a862-c3ba2f70b6b3@linuxfoundation.org> (raw) Linux Kernel Code of Conduct Committee: April 30 2021 In the period of November 1, 2020 through April 30, 2021 the Code of Conduct Committee received the following reports: Unacceptable behavior or comments in email (3rd party): 4 The result of the investigation: - Education and coaching: 1 - Public response to call attention to the behavior and request correction with consequence of ban if behavior persists: 1 - Public response to attention to the behavior and request correction: 1 - Clarification on the Code of Conduct conduct related to maintainer rights and responsibility to reject code: 1 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>. ----------------------- This report and the past Code Of Conduct Committee reports can be found on the Code of Conduct website at https://www.kernel.org/code-of-conduct.html thanks, -- Shuah (On behalf of the Code of Conduct Committee)
WARNING: multiple messages have this Message-ID (diff)
From: Shuah Khan <skhan@linuxfoundation.org> To: linux-kernel@vger.kernel.org Cc: "conduct@kernel.org" <conduct@kernel.org>, tech-board-discuss@lists.linuxfoundation.org Subject: [Tech-board-discuss] Linux Kernel Code of Conduct Committee: April 2021 report Date: Tue, 18 May 2021 13:09:29 -0600 [thread overview] Message-ID: <448b06e4-41fc-26df-a862-c3ba2f70b6b3@linuxfoundation.org> (raw) Linux Kernel Code of Conduct Committee: April 30 2021 In the period of November 1, 2020 through April 30, 2021 the Code of Conduct Committee received the following reports: Unacceptable behavior or comments in email (3rd party): 4 The result of the investigation: - Education and coaching: 1 - Public response to call attention to the behavior and request correction with consequence of ban if behavior persists: 1 - Public response to attention to the behavior and request correction: 1 - Clarification on the Code of Conduct conduct related to maintainer rights and responsibility to reject code: 1 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>. ----------------------- This report and the past Code Of Conduct Committee reports can be found on the Code of Conduct website at https://www.kernel.org/code-of-conduct.html thanks, -- Shuah (On behalf of the Code of Conduct Committee)
next reply other threads:[~2021-05-18 19:09 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-18 19:09 Shuah Khan [this message] 2021-05-18 19:09 ` [Tech-board-discuss] Linux Kernel Code of Conduct Committee: April 2021 report 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=448b06e4-41fc-26df-a862-c3ba2f70b6b3@linuxfoundation.org \ --to=skhan@linuxfoundation.org \ --cc=conduct@kernel.org \ --cc=linux-kernel@vger.kernel.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: linkBe 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.