From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> To: James Bottomley <James.Bottomley@HansenPartnership.com> Cc: linux-kernel <linux-kernel@vger.kernel.org>, ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [PATCH v2 3/3] code-of-conduct: Add back the TAB as the central reporting point Date: Wed, 10 Oct 2018 17:04:56 -0400 [thread overview] Message-ID: <20181010210456.GB30366@char.us.oracle.com> (raw) In-Reply-To: <1539202230.12644.12.camel@HansenPartnership.com> On Wed, Oct 10, 2018 at 01:10:30PM -0700, James Bottomley wrote: > Add a Reporting section where the Enforcement section used to be. The > intention is still to debate what should go here, but in the meantime, this > gives us back the central reporting point we had in the old code of conflict. > Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Thank you! > Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com> > > --- > > v2: Added this patch to allay concerns we were stripping the reporting > mechanism entirely. > --- > Documentation/process/code-of-conduct.rst | 10 ++++++++++ > 1 file changed, 10 insertions(+) > > diff --git a/Documentation/process/code-of-conduct.rst b/Documentation/process/code-of-conduct.rst > index 4dd90987305b..2000bdc2a6ad 100644 > --- a/Documentation/process/code-of-conduct.rst > +++ b/Documentation/process/code-of-conduct.rst > @@ -59,6 +59,16 @@ address, posting via an official social media account, or acting as an appointed > representative at an online or offline event. Representation of a project may be > further defined and clarified by project maintainers. > > +Reporting > +========= > + > +Instances of abusive, harassing, or otherwise unacceptable behavior may be > +reported by contacting the Technical Advisory Board (TAB) at > +<tab@lists.linux-foundation.org>. All complaints will be reviewed and > +investigated and will result in a response that is deemed necessary and > +appropriate to the circumstances. The TAB is obligated to maintain > +confidentiality with regard to the reporter of an incident. > + > Attribution > =========== > > -- > 2.13.7 >
WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> To: James Bottomley <James.Bottomley@HansenPartnership.com> Cc: ksummit-discuss@lists.linuxfoundation.org, linux-kernel <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v2 3/3] code-of-conduct: Add back the TAB as the central reporting point Date: Wed, 10 Oct 2018 17:04:56 -0400 [thread overview] Message-ID: <20181010210456.GB30366@char.us.oracle.com> (raw) In-Reply-To: <1539202230.12644.12.camel@HansenPartnership.com> On Wed, Oct 10, 2018 at 01:10:30PM -0700, James Bottomley wrote: > Add a Reporting section where the Enforcement section used to be. The > intention is still to debate what should go here, but in the meantime, this > gives us back the central reporting point we had in the old code of conflict. > Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Thank you! > Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com> > > --- > > v2: Added this patch to allay concerns we were stripping the reporting > mechanism entirely. > --- > Documentation/process/code-of-conduct.rst | 10 ++++++++++ > 1 file changed, 10 insertions(+) > > diff --git a/Documentation/process/code-of-conduct.rst b/Documentation/process/code-of-conduct.rst > index 4dd90987305b..2000bdc2a6ad 100644 > --- a/Documentation/process/code-of-conduct.rst > +++ b/Documentation/process/code-of-conduct.rst > @@ -59,6 +59,16 @@ address, posting via an official social media account, or acting as an appointed > representative at an online or offline event. Representation of a project may be > further defined and clarified by project maintainers. > > +Reporting > +========= > + > +Instances of abusive, harassing, or otherwise unacceptable behavior may be > +reported by contacting the Technical Advisory Board (TAB) at > +<tab@lists.linux-foundation.org>. All complaints will be reviewed and > +investigated and will result in a response that is deemed necessary and > +appropriate to the circumstances. The TAB is obligated to maintain > +confidentiality with regard to the reporter of an incident. > + > Attribution > =========== > > -- > 2.13.7 >
next prev parent reply other threads:[~2018-10-10 21:05 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-10 20:07 [Ksummit-discuss] [PATCH v2 0/3] code of conduct fixes James Bottomley 2018-10-10 20:07 ` James Bottomley 2018-10-10 20:08 ` [Ksummit-discuss] [PATCH v2 1/3] code-of-conduct: Fix the ambiguity about collecting email addresses James Bottomley 2018-10-10 20:08 ` James Bottomley 2018-10-10 22:17 ` [Ksummit-discuss] " Eric W. Biederman 2018-10-10 22:17 ` Eric W. Biederman 2018-10-11 2:33 ` Mauro Carvalho Chehab 2018-10-11 2:33 ` Mauro Carvalho Chehab 2018-10-15 20:58 ` Kees Cook 2018-10-15 20:58 ` Kees Cook 2018-10-10 20:09 ` [Ksummit-discuss] [PATCH v2 2/3] code-of-conduct: Strip the enforcement paragraph pending community discussion James Bottomley 2018-10-10 20:09 ` James Bottomley 2018-10-10 21:04 ` [Ksummit-discuss] " Luck, Tony 2018-10-10 21:04 ` Luck, Tony 2018-10-10 21:19 ` James Bottomley 2018-10-10 21:19 ` James Bottomley 2018-10-10 21:28 ` Luck, Tony 2018-10-10 21:28 ` Luck, Tony 2018-10-15 21:02 ` Kees Cook 2018-10-15 21:02 ` Kees Cook 2018-10-11 2:37 ` Mauro Carvalho Chehab 2018-10-11 2:37 ` Mauro Carvalho Chehab 2018-10-10 20:10 ` [Ksummit-discuss] [PATCH v2 3/3] code-of-conduct: Add back the TAB as the central reporting point James Bottomley 2018-10-10 20:10 ` James Bottomley 2018-10-10 20:13 ` [Ksummit-discuss] " Alan Cox 2018-10-10 20:13 ` Alan Cox 2018-10-11 2:30 ` [Ksummit-discuss] " Mauro Carvalho Chehab 2018-10-11 6:50 ` Geert Uytterhoeven 2018-10-11 6:50 ` Geert Uytterhoeven 2018-10-10 21:04 ` Konrad Rzeszutek Wilk [this message] 2018-10-10 21:04 ` Konrad Rzeszutek Wilk 2018-10-10 23:23 ` [Ksummit-discuss] [PATCH v2 0/3] code of conduct fixes Eric W. Biederman 2018-10-10 23:23 ` Eric W. Biederman 2018-10-10 23:41 ` Al Viro 2018-10-10 23:41 ` Al Viro 2018-10-11 0:00 ` James Bottomley 2018-10-11 3:11 ` Mauro Carvalho Chehab 2018-10-11 3:11 ` Mauro Carvalho Chehab 2018-10-11 10:43 ` Rainer Fiebig 2018-10-11 6:39 ` Tomi Valkeinen
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=20181010210456.GB30366@char.us.oracle.com \ --to=konrad.wilk@oracle.com \ --cc=James.Bottomley@HansenPartnership.com \ --cc=ksummit-discuss@lists.linuxfoundation.org \ --cc=linux-kernel@vger.kernel.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.