From: Greg KH <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: tech-board-discuss@lists.linuxfoundation.org
Subject: Linux Kernel Code of Conduct Committee: December 2019 report
Date: Fri, 3 Jan 2020 11:56:14 +0100 [thread overview]
Message-ID: <20200103105614.GC1047442@kroah.com> (raw)
In the spirit of getting into a proper cycle for the reports, here's the
end of 2019 status so that we can start fresh with January 2020 and get
on to the normally scheduled report schedule.
Linux Kernel Code of Conduct Committee: December 2019
In the period of December 1, 2019 through December 30, 2019 the Committee
received the following report:
- Insulting behavior in email: 1
The result of the investigation:
- Education and coaching: 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>.
------------
Side-note, the website at https://www.kernel.org/code-of-conduct.html is
now up to date and this, and all future reports will also be published
there.
thanks,
greg k-h
reply other threads:[~2020-01-03 10:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200103105614.GC1047442@kroah.com \
--to=gregkh@linuxfoundation.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: 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 NNTP newsgroup(s).