diff --git a/llvm/docs/CodeOfConduct.rst b/llvm/docs/CodeOfConduct.rst --- a/llvm/docs/CodeOfConduct.rst +++ b/llvm/docs/CodeOfConduct.rst @@ -97,7 +97,7 @@ If you believe someone is violating the code of conduct you can always report it to the LLVM Foundation Code of Conduct Committee by emailing -conduct@llvm.org. All reports will be kept confidential. This isn’t a public +conduct@llvm.org. All reports will be kept confidential. This isn't a public list and only members of the advisory committee will receive the report. For details on what to include in the report, please see the :doc:`Reporting Guide `. diff --git a/llvm/docs/ReportingGuide.rst b/llvm/docs/ReportingGuide.rst --- a/llvm/docs/ReportingGuide.rst +++ b/llvm/docs/ReportingGuide.rst @@ -23,17 +23,19 @@ irc/discord/slack, etc) we ask that you make any reports by emailing conduct@llvm.org. This is received by all members of the CoC 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 +* For LLVM Developers’ Meetings, please file a report with the on-site Code + of Conduct team. 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, 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. + reported in-person at a LLVM Developers’ Meeting will be emailed to the + Code of Conduct Committee. -* For meetups, please report the incident to the local meetup organizers first and then email conduct@llvm.org with your report. Each meetup will have a +* For meetups, please report the incident to the local meetup organizers first + and then email conduct@llvm.org with your report. Each meetup will have a 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@llvm.org. All meetup organizers who receive an in + not well handled by the local organizers, please include this information in + your email to conduct@llvm.org. All meetup organizers who receive an in person report are also asked to email conduct@llvm.org with the incident information. @@ -43,7 +45,7 @@ appropriate, please include this in your report and we will attempt to notify them. -Guidelines For Reporting Incidents +Guidelines for Reporting Incidents ================================== Please email conduct@llvm.org with the following details (if possible): diff --git a/llvm/docs/ResponseGuide.rst b/llvm/docs/ResponseGuide.rst --- a/llvm/docs/ResponseGuide.rst +++ b/llvm/docs/ResponseGuide.rst @@ -29,7 +29,7 @@ .. _Receiving a report: -Receiving a report +Receiving a Report ================== Reports are typically received by email (conduct@llvm.org) or in person from @@ -41,7 +41,7 @@ will be taken. Specific guidance is in the checklist below. 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 +to the Code of Conduct committee within 24 hours by the on-site CoC response team. @@ -50,7 +50,7 @@ Immediate Response Checklist ============================ -The CoC committee generally works, decides and communicates together. If the +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 @@ -64,15 +64,14 @@ removal, or moderation) may be used to immediately stop it. * For events that include talks, organizers should end talks early if the 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. + other types of code of conduct violations occur and organizers should do + their best to determine if a talk should be ended early or not. When undertaking an immediate response, document the action and notify the committee within 24 hours. -Response procedure +Response Procedure ================== The following is a summary of the steps the committee takes when responding to @@ -136,8 +135,8 @@ * Determine if it violated the CoC and specifically which part. * Consult documentation of past incidents for patterns of behavior (if available and applicable). -* Follow up with the reportee. Allow a reasonable fixed time for reportee to - respond with their view or any other additional information. +* Follow up with the reportee to get their view or any other additional + information. * Determine appropriate resolutions to the incident when all information has been gathered. * Notify the reporter of the resolution and request feedback. This may or may @@ -161,8 +160,8 @@ * Reiterate the Code of Conduct and that their behavior may be deemed inappropriate. * 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 CoC + committee determine there is a breach. The reportee will be given a week to respond with the option to request additional time if needed and subject to approval of the CoC Committee. @@ -186,8 +185,7 @@ violation. * A private verbal warning and/or reprimand from the committee to the 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. + may happen in person, email, by phone, video chat, or IRC. * Request that the reportee avoid any interaction with, and physical proximity to, another person for the remainder of the event. * Refusal of alcoholic beverage purchases by the reportee at LLVM events. @@ -199,7 +197,7 @@ * Requiring that the reportee immediately leave an event and not return. * Immediately ending any volunteer responsibilities and privileges the reportee holds. -* An imposed suspension (e.g., asking someone to “take a week off” from mailing +* An imposed suspension (e.g., 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 @@ -222,9 +220,10 @@ The email should include documentation related to the incident to support the appeal. The said documentation may include, but does not have to be limited to: + * Information from the reportee justifying reasoning for the appeal. * Statements from other individuals involved in the incident to support the -* appeal. + appeal. Appeals can be requested up to 30 days after a resolution has been communicated to the individual(s). The committee will aim to evaluate appeals within two weeks of receipt. In the event that appeal can not be evaluated within that time, the CoC committee will respond with an updated and projected timeline. @@ -258,7 +257,7 @@ =============== 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 +Conduct committee members. However, the Code of Conduct Committee will always comply with law enforcement when directed. In the case that a CoC committee member is involved in a report, the member will be asked to recuse themselves from ongoing conversations, and they will not have access to reports after the @@ -287,7 +286,7 @@ * An overview of the reports received, and resolutions. * A more detailed summary of each reported incident and the resolution while -* maintaining confidentiality. + maintaining confidentiality. These reports will be published on the LLVM website.