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

Got halfway through so far. Some editorial comments.



================
Comment at: llvm/docs/CodeOfConduct.rst:123
+The committee will consist of a mininum of 5 members and members are asked to
+serve at least a 1 year term. New commitee members will be selected by the
+current committee and the LLVM Foundation Board of Directors.
----------------
Minor: Spelling correction.


================
Comment at: llvm/docs/ReportingGuide.rst:26
 
-* For a LLVM Developers’ Meeting has a Code of Conduct team. For each conference, their names and contact details are listed on the event webpage. You can also approach any other staff member, who can be identified by special badges and often found at the registration desk. All incidents reported in person at a  LLVM Developers’ Meeting will be emailed to the Code of Conduct Committee. 
+* For a LLVM Developers’ Meeting has a Code of Conduct team. For each 
+  conference, their names and contact details are listed on the event 
----------------
Fix possible typo that causes an incomplete sentence.


================
Comment at: llvm/docs/ReportingGuide.rst:31
+  to help you locate a member of the Code of Conduct team. All incidents 
+  reported in person at a  LLVM Developers’ Meeting will be emailed to 
+  the Code of Conduct Committee. 
----------------
Minor: Fix mid-sentence double space.


================
Comment at: llvm/docs/ReportingGuide.rst:34
 
-* For meetups, please report the incident to the local meetup organizers first. Each meetup will have a contact listed on the associated meetup page. If you feel uncomfortable with this or if you feel the incident was not well handled by the local organizers, please email conduct at llvm.org. All meetup organizers who receive an in person report are asked to email conduct at llvm.org with the incident information.
+* For meetups, please report the incident to the local meetup organizers first   and then email conduct at llvm.org with your report. Each meetup will have a 
+  contact listed on the associated meetup page. If you feel the incident was 
----------------
Minor: Formatting fix.


================
Comment at: llvm/docs/ReportingGuide.rst:36-37
+  contact listed on the associated meetup page. If you feel the incident was 
+  not well handled by the local organizers, please include this information in   your email to conduct at llvm.org. All meetup organizers who receive an in 
+  person report are also asked to email conduct at llvm.org with the
+  incident information.
----------------
Fix formatting.
s/in person/in-person/;


================
Comment at: llvm/docs/ReportingGuide.rst:46
 
-Guidelines for reporting incidents
+Guidelines For Reporting Incidents
 ==================================
----------------
Minor: Many style guides would not capitalize "for" in title case.


================
Comment at: llvm/docs/ResponseGuide.rst:32
 
 Receiving a report
 ==================
----------------
Unaddressed instance of Aaron's comment about applying title case consistently.


Repository:
  rG LLVM Github Monorepo

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

https://reviews.llvm.org/D122937