[lkml]   [2018]   [Oct]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
Subject[PATCH v3 3/3] code-of-conduct: Add back the TAB as the central reporting point
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 <>
Reviewed-by: Mauro Carvalho Chehab <>
Acked-by: Geert Uytterhoeven <>
Signed-off-by: James Bottomley <>


v2: Added this patch to allay concerns we were stripping the reporting
mechanism entirely.
v3: Add (where required by law) as a qualifier to the confidentiality
Documentation/process/code-of-conduct.rst | 11 +++++++++++
1 file changed, 11 insertions(+)

diff --git a/Documentation/process/code-of-conduct.rst b/Documentation/process/code-of-conduct.rst
index 4dd90987305b..eec768471a4d 100644
--- a/Documentation/process/code-of-conduct.rst
+++ b/Documentation/process/code-of-conduct.rst
@@ -59,6 +59,17 @@ 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.

+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the Technical Advisory Board (TAB) at
+<>. 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 (except where
+required by law).

 \ /
  Last update: 2018-10-16 17:01    [W:0.067 / U:15.512 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site