Stress Testing Your Code of Conduct in Production
summary
Organizers present a concrete, reproducible CoC response: a documented step‑by‑step process, a public handbook repository with reusable incident report template and email templates, and operational practices like a private Slack channel, two‑person discrete meetings and published transparency report. Lessons learned across five major conferences show failures too — missing a dedicated CoC email, understaffed teams, unclear boundaries for online spaces and parties — and the process helps reduce improvisation though it does not eliminate mistakes.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:56History of Code of Conduct
- 6:45Our Mistakes
- 13:13Plan for Failure
- 14:17What Matters
- 16:20The Response Team
- 17:36Screenshots
- 18:22Meeting
- 19:14Incident Report
- 23:12Code of Conduct Handbook
- 24:47Recap
related talks
20mFostering Community Health and demystifying the CWG
43mThe 10 Commandments of Community Organizing
42mHow to foster a Culture of Resilience
21mA Playbook for Effective Corporate Communication After a Cyber Security Incident
24mConcrete Steps to Create a Security Culture
28mBuilding a healthy on-call culture
30mHow to Drive Consensus & Transparency in OpenSource Communities
20mConducting Humane Code Reviews