[PATCH] D122937: Provide the complete response and reporting Code of Conduct documentation. Remove the word draft from all documents, add information about the CoC committee expectations and add a place for transparency reports.

Mehdi AMINI via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Sun Apr 3 18:21:22 PDT 2022


mehdi_amini added a comment.

It's great to finally see this coming out of "draft mode" :)



================
Comment at: llvm/docs/ResponseGuide.rst:92
+
+
+The committee will aim to have a resolution agreed upon within two weeks of receipt of the incident report. In the event that a resolution cannot be determined within that time, the CoC committee will respond to the reporter(s) with an updated and projected timeline for resolution. 
----------------
Is the double empty line intentional?



================
Comment at: llvm/docs/ResponseGuide.rst:127
+* An imposed suspension (i.e. asking someone to “take a week off” from mailing lists, bug tracker, IRC, Discord, repositories, or other communication forms). 
+* A permanent or temporary ban from some or all LLVM Project spaces (online or in person).
+
----------------
Does that include forbidding someone to send a patch to the project for example? What if this person published a patch, can someone else still cherry-pick it in the repo with the author attribution?

(I would think that a very extreme situation would be needed to trigger such a response anyway)


================
Comment at: llvm/docs/ResponseGuide.rst:129
+
+
+Once a resolution is agreed upon, but before it is enacted, the committee will contact the reporter and any other affected parties to explain the proposed resolution. They will ask if this resolution is acceptable and must note feedback for the record. However, the committee is not required to act on this feedback.
----------------
Is the double empty line intentional?


================
Comment at: llvm/docs/ResponseGuide.rst:177
+.. _Write The Docs Response Guide: https://www.writethedocs.org/code-of-conduct/#guidelines-for-reporting-incidents
+
----------------
Formatting nit: this may not be very important, but this file does not have an empty line after the section titles.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D122937/new/

https://reviews.llvm.org/D122937



More information about the llvm-commits mailing list