[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.

[Hubert Tong via Phabricator via llvm-commits]

hubert.reinterpretcast added a comment.

Some more editorial comments and a comment regarding some text that does not seem to convey whatever meaning was intended well.



================
Comment at: llvm/docs/ResponseGuide.rst:44
+For in-person events that have a violation reported, the report should be sent
+to the Code of Conduct committee within 24 hours by the on site CoC response
+team. 
----------------
Prior comment missed?
Grammar: s/on site/on-site/;


================
Comment at: llvm/docs/ResponseGuide.rst:66-69
+  violations include harassment or violent threats. There may be talks where
+  other types of code of conduct violations or they are infrequent,  and
+  organizers should do their best to determine if a talk should be ended early
+  or not. 
----------------
Prior comment missed?

I still don't know what this is trying to say. Organizers should use discretion in determining whether a talk should be ended early if Code of Conduct violations other than (any single instance) of harassment or violent threats has occurred? What does the "or they are infrequent" refer to?

Is the intent that the sentence about harassment of violent treats applies only to repeated or ongoing cases?



================
Comment at: llvm/docs/ResponseGuide.rst:75
 
 Response procedure
 ==================
----------------
Minor: Title case.


================
Comment at: llvm/docs/ResponseGuide.rst:164-165
 * Give them the opportunity to state their view of the incident.
-* Explain the possible resolutions that may be enforced should the CoCc determine there is a breach.
+* Explain the possible resolutions that may be enforced should the CoCc
+  determine there is a breach.
 
----------------
Prior comment missed?

"CoCc" is not used anywhere else in this patch.
s/CoCc/CoC Committee/;


================
Comment at: llvm/docs/ResponseGuide.rst:189
+  individual(s) involved and request to stop this behavior. This conversation
+* may happen in person, by phone, video chat, or IRC. If the individual refuses
+  those options, an email will be sent.
----------------
Inadvertent new bullet point?


================
Comment at: llvm/docs/ResponseGuide.rst:261
+All reports will be kept confidential with details shared only with the Code of
+Conduct committee members. However, The Code of Conduct Committee will always
+comply with law enforcement when directed. In the case that a CoC committee
----------------
Minor: Use lowercase "the", which would be consistent with other similar uses in this patch.


================
Comment at: llvm/docs/ResponseGuide.rst:290
+* A more detailed summary of each reported incident and the resolution while
+* maintaining confidentiality.
 
----------------
Inadvertent new bullet point?


================
Comment at: llvm/docs/ResponseGuide.rst:40
+
+The CoC committee generally works, decides and communicates together. If the report indicates that an immediate response is required and other committee members are not available, any committee member may take the immediate action they think is necessary. In-person Code of Conduct response teams should use this checklist to determine if an immediate response is needed.
+
----------------
aaron.ballman wrote:
> I <3 Oxford commas, no idea if others love them as much as I do.
I guess we aren't using "Oxford commas"?


Repository:
  rG LLVM Github Monorepo

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

https://reviews.llvm.org/D122937