How to Report Violations of the Community Participation Guidelines

This document provides high-level information, for understanding and reporting violations of Mozilla's Community Participation Guidelines.

From the Community Participation Guidelines:

The heart of Mozilla is people. We put people first and do our best to recognize, appreciate and respect the diversity of our global contributors. The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community. As such, we have adopted this code of conduct and require all those who participate to agree and adhere to these Community Participation Guidelines in order to help us create a safe and positive community experience for all.

This document is intended as an interface to existing documents, processes and people responsible for ensuring Mozilla’s communities are healthy, and inclusive for all.

When To Report

Please report all incidents where someone has engaged in behavior that is potentially illegal or makes you or someone else feel unsafe, unwelcome or uncomfortable as further explained in the CPG.

How to Give a Report

If you believe someone is in physical danger, call your local emergency number.

If you have a report by and about a contributor (for example, the report is made by one contributor about another contributor), then you should make your report at the cpg-report@mozilla.com.

If you have a report involving an employee, contractor, or vendor (for example, the report is made by an employee or is about an employee), then you should report at the Mozilla Employee hotline.

Put another way…

If someone reports to you…

• Do not question, or judge their experience.
• Do not invite them to withdraw the incident report.
• Do not promise any particular response.
• Do let them know that for Mozilla’s policy to be impactful, reports should go through the hotline/email. If they do not feel comfortable filing the report themselves, you may do so.

No matter who files the report, the information below is important to capture.

• Names of the people involved (or if names are unknown, use descriptions and any identifiable info such as appearance, role, handle, project/community affiliation).
• Description of incident, including memorable dates (or events) and locations.
• If the reporter wants to make an anonymous report, please inform them that without contact information we may not be able to update the initial reporter when appropriate. Some laws prohibit anonymous reporting and that you may be required to provide their name if you are a Mozilla Manager or Community Leader.
• Relationship of reporter/victim.

Mozilla Managers and Community leaders

If a Mozilla Manager or Community leader is informed about potential CPG violations, they are expected to immediately report the incident through the applicable email/hotline, even if the initial reporter will also file a report. Mozilla Managers and Community leaders are not permitted to investigate complaints on their own.

Do not impose your own judgement on how the reporter should react. Focus on listening.

What happens after the report is filed

Investigation

Reports are handled discretely and privately, and will only be shared with the people who can investigate, respond, and advise. As part of this investigation, it may be necessary for some information to be disclosed to others, for example, to key stakeholders administering communities or events, witnesses, and the wrongdoers.

Correspondence

All reports are reviewed and responded to based on the nature of the report and we try to provide reasonably timed updates as part of open investigations.

Redress

When an investigation is complete, to the extent the wrongdoer is subject to Mozilla’s control, appropriate measures will be taken to address the situation.

No Retaliation

Mozilla does not tolerate retaliation against Mozillians who report concerns under the CPG in good faith. Acts of retaliation should be reported in the same process as described above.

License

This document includes content forked from the PyCon Code of Conduct Revision 2f4d980 which is licensed under a Creative Commons Attribution 3.0 Unported License.

This document is licensed under a Creative Commons Attribution 3.0 Unported License.