123 lines · plain
1..2 This work is licensed under a Creative Commons Attribution 3.0 Unported License.3 SPDX-License-Identifier: CC-BY-3.04 5=================================6LLVM CoC Incident Reporting Guide7=================================8 9First of all, please do not feel like you may be a burden to us by reporting10incidents. We consider reports an opportunity for us to act: by knowing about11an incident, we can act on it if appropriate, and reduce continuation of12problematic behavior. If we don't know, we can't learn or take any appropriate13actions.14 15If you are not sure the situation being reported was a :doc:`Code of16Conduct<CodeOfConduct>` violation, we encourage you to still report it. We17would much rather have reports where we decide to take no action, rather than18miss a report of an actual violation. There is no harm in reporting an incident19which is later determined not to be a violation, and knowing about incidents20that are not violations can also help us to improve the Code of Conduct or the21processes surrounding it.22 23Reporting and Contact Information24=================================25 26* For any incident involving an online platform (e.g., mailing lists, forums, 27 irc/discord/slack, etc) we ask that you make any reports by emailing 28 conduct@llvm.org. This is received by all members of the CoC Committee.29 30* For LLVM Developers' Meetings, please file a report with the on-site Code 31 of Conduct team. Their names and contact details are listed on the event 32 webpage. You can also approach any other staff member, who can be 33 identified by special badges and often found at the registration desk, 34 to help you locate a member of the Code of Conduct team. All incidents 35 reported in-person at a LLVM Developers' Meeting will be emailed to the 36 Code of Conduct Committee. 37 38* For meetups, please report the incident to the local meetup organizers first39 and then email conduct@llvm.org with your report. Each meetup will have a 40 contact listed on the associated meetup page. If you feel the incident was 41 not well handled by the local organizers, please include this information in42 your email to conduct@llvm.org. All meetup organizers who receive an 43 in-person report are also asked to email conduct@llvm.org with the44 incident information.45 46 47If you believe anyone is in physical danger, please notify appropriate law48enforcement first. If you are unsure what law enforcement agency is49appropriate, please include this in your report and we will attempt to notify50them.51 52Guidelines for Reporting Incidents53==================================54 55Please email conduct@llvm.org with the following details (if possible):56 57* Your contact info (so we can get in touch with you). Include email and58 optionally a phone number.59* Names or descriptions of anyone who was involved or who witnessed the60 incident.61* When and where the incident occurred. Please be as specific as possible.62* Your account of what occurred. If there is a written record (e.g. emails,63 forum links, tweets, Slack, or Discord messages) please include screenshots,64 as well as any available link.65* Any extra context you believe existed for the incident.66* If you believe this incident is ongoing.67* If you have concerns about retaliation or your personal safety, please note68 those concerns in your report.69* Any other information you believe we should have.70 71If you are unable to provide all of this information, please still make the72report and include as much information as you have.73 74When handling a report, we follow our :doc:`Response Guide <ResponseGuide>`.75 76Confidentiality77===============78 79All reports will be kept confidential with details shared only with the Code of80Conduct committee members. In the case that a CoC committee member is involved81in a report, the member will be asked to recuse themselves from ongoing82conversations, and they will not have access to any reports at any time.83Resolution action may also include removal of that member from the CoC84committee.85 86Some incidents happen in one-on-one interactions, and though details are87anonymized, the reported person may be able to guess who made the report. If88you have concerns about retaliation or your personal safety, please note those89concerns in your report. You are still encouraged to report the incident so90that we can support you while keeping our community members safe. In some91cases, we can compile several anonymized reports into a pattern of behavior,92and take action on that pattern. 93 94Transparency reports will be published but will retain confidentiality. See the95:doc:`Response Guide <ResponseGuide>`. for details on this.96 97Following Up With Reporter(s)98=============================99 100Once a report is filed, the Code of Conduct committee will handle the review101and follow up according to the procedures in the :doc:`Response Guide102<ResponseGuide>`. 103 104 105Thanks!106=======107 108This guide was created and inspired by the following: the `Django Project`_,109`Carpentries Response Guide`_, and the `Write The Docs Response Guide`_.110 111License112=======113 114All content on this page is licensed under a `Creative Commons Attribution 3.0115Unported License`_.116 117 118.. _Django Project: https://www.djangoproject.com/conduct/119.. _Carpentries Response Guide: https://docs.carpentries.org/topic_folders/policies/enforcement-guidelines.html120.. _Write The Docs Response Guide: https://www.writethedocs.org/code-of-conduct/#guidelines-for-reporting-incidents121.. _Creative Commons Attribution 3.0 Unported License: http://creativecommons.org/licenses/by/3.0/122 123