If you notice a dangerous situation, someone in distress, or violations of the Donut.js Code of Conduct, even if they seem inconsequential, please report it as soon as possible. You can contact us through:
All reports will be kept confidential. In some cases we may determine that a public statement will need to be made. If that’s the case, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise.
If you believe anyone is in physical danger, please notify appropriate emergency services first. If you are unsure what service or agency is appropriate to contact, include this in your report and we will attempt to notify them.
In your report, please include:
You will receive a response from Donut.js acknowledging receipt as soon as possible, but within 2 business days.
Donut.js Code of Conduct responders will review the incident and determine:
If this is determined to be an ongoing incident or a threat to physical safety, the team’s immediate priority will be to protect everyone involved. This means we may delay an “official” response until we believe that the situation has ended and that everyone is physically safe.
Once the team has a complete account of the events, we will make a decision as to how to respond. Responses may include:
We’ll respond within one week to the person who filed the report with either a resolution or an update on the situation. Reporter feedback may be factored into our next steps, with the final action determined by the Donut.js Code of Conduct responders.
The response team will make a summary report of the situation to the Donut.js lead organizers. The organizers may choose to issue a public report of the incident or take additional actions.
Only permanent resolutions (such as bans) may be appealed. To appeal a decision of the working group, contact the Donut.js Code of Conduct response team at email@example.com with your appeal and Donut.js lead organizers and Code of Conduct response team will review the case together.
Version 1, adopted by the Donut.js lead organizers and Code of Conduct response team on July 26, 2018. Posted July 26, 2018.