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 <[email protected]>
Thank you! > Signed-off-by: James Bottomley <[email protected]> > > --- > > 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 > +<[email protected]>. 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 >
