Regular transparency reports by CoC WG

[nainar]

Several conferences have published "transparency reports," anonymized summaries of all the code of conduct reports related to the conference, along with the actions taken by the conference code of conduct committee. We on the Code of Conduct WG this is a great idea to incorporate not just for all AMP conferences, but for the greater open source project.

Examples of Conduct Transparency Reports(1)

• DjangoCon Europe 2018
• PyCon 2018 Code of Conduct Transparency Report
• 2018 Code for America Summit

Why do we need a transparency report? (2)

• Public enforcement allows the community to keep an eye on enforcement and course correct if the code of conduct is being enforced poorly or in a biased manner.
• Publicizing a situation in which the community swiftly and effectively handled a code of conduct violation is usually a net positive for a community's reputation. Trying to keep reports secret or refusing to comment on them publicly is usually a negative mark or a danger sign for a community.
• Marginalized people already know that harassment happens in all communities, and they are looking for a community that handles harassment openly and in a forthright manner, instead of ignoring,hiding, or downplaying them.

(1) This list is not an endorsement of these reports but just to allow the reader to get an idea
(2) Lifted verbatim from How to Respond to Code of Conduct Reports by Valerie Aurora and Mary Gardiner

[nainar]

/cc @jpettitt @danielrozenberg @estherkim

[rudygalfi]

Have you established a cadence (e.g. annual?) and timing for release of a transparency report?