1================================= 2LLVM CoC Incident Reporting Guide 3================================= 4 5First of all, please do not feel like you may be a burden to us by reporting 6incidents. We consider reports an opportunity for us to act: by knowing about 7an incident, we can act on it if appropriate, and reduce continuation of 8problematic behavior. If we don't know, we can't learn or take any appropriate 9actions. 10 11If you are not sure the situation being reported was a :doc:`Code of 12Conduct<CodeOfConduct>` violation, we encourage you to still report it. We 13would much rather have reports where we decide to take no action, rather than 14miss a report of an actual violation. There is no harm in reporting an incident 15which is later determined not to be a violation, and knowing about incidents 16that are not violations can also help us to improve the Code of Conduct or the 17processes surrounding it. 18 19Reporting and Contact Information 20================================= 21 22* For any incident involving an online platform (e.g., mailing lists, forums, 23 irc/discord/slack, etc) we ask that you make any reports by emailing 24 conduct@llvm.org. This is received by all members of the CoC Committee. 25 26* For LLVM Developers' Meetings, please file a report with the on-site Code 27 of Conduct team. Their names and contact details are listed on the event 28 webpage. You can also approach any other staff member, who can be 29 identified by special badges and often found at the registration desk, 30 to help you locate a member of the Code of Conduct team. All incidents 31 reported in-person at a LLVM Developers' Meeting will be emailed to the 32 Code of Conduct Committee. 33 34* For meetups, please report the incident to the local meetup organizers first 35 and then email conduct@llvm.org with your report. Each meetup will have a 36 contact listed on the associated meetup page. If you feel the incident was 37 not well handled by the local organizers, please include this information in 38 your email to conduct@llvm.org. All meetup organizers who receive an 39 in-person report are also asked to email conduct@llvm.org with the 40 incident information. 41 42 43If you believe anyone is in physical danger, please notify appropriate law 44enforcement first. If you are unsure what law enforcement agency is 45appropriate, please include this in your report and we will attempt to notify 46them. 47 48Guidelines for Reporting Incidents 49================================== 50 51Please email conduct@llvm.org with the following details (if possible): 52 53* Your contact info (so we can get in touch with you). Include email and 54 optionally a phone number. 55* Names or descriptions of anyone who was involved or who witnessed the 56 incident. 57* When and where the incident occurred. Please be as specific as possible. 58* Your account of what occurred. If there is a written record (e.g. emails, 59 forum links, tweets, Slack, or Discord messages) please include screenshots, 60 as well as any available link. 61* Any extra context you believe existed for the incident. 62* If you believe this incident is ongoing. 63* If you have concerns about retaliation or your personal safety, please note 64 those concerns in your report. 65* Any other information you believe we should have. 66 67If you are unable to provide all of this information, please still make the 68report and include as much information as you have. 69 70When handling a report, we follow our :doc:`Response Guide <ResponseGuide>`. 71 72Confidentiality 73=============== 74 75All reports will be kept confidential with details shared only with the Code of 76Conduct committee members. In the case that a CoC committee member is involved 77in a report, the member will be asked to recuse themselves from ongoing 78conversations, and they will not have access to any reports at any time. 79Resolution action may also include removal of that member from the CoC 80committee. 81 82Some incidents happen in one-on-one interactions, and though details are 83anonymized, the reported person may be able to guess who made the report. If 84you have concerns about retaliation or your personal safety, please note those 85concerns in your report. You are still encouraged to report the incident so 86that we can support you while keeping our community members safe. In some 87cases, we can compile several anonymized reports into a pattern of behavior, 88and take action on that pattern. 89 90Transparency reports will be published but will retain confidentiality. See the 91:doc:`Response Guide <ResponseGuide>`. for details on this. 92 93Following Up With Reporter(s) 94============================= 95 96Once a report is filed, the Code of Conduct committee will handle the review 97and follow up according to the procedures in the :doc:`Response Guide 98<ResponseGuide>`. 99 100 101Thanks! 102======= 103This guide was created and inspired by the following: the `Django Project`_, 104`Carpentries Response Guide`_, and the `Write The Docs Response Guide`_. 105 106.. _Django Project: https://www.djangoproject.com/conduct/ 107.. _Carpentries Response Guide: https://docs.carpentries.org/topic_folders/policies/enforcement-guidelines.html 108.. _Write The Docs Response Guide: https://www.writethedocs.org/code-of-conduct/#guidelines-for-reporting-incidents 109 110