Why We Need Codes of Conduct, and Why They're Not Enough
summary
Argues that a code of conduct is inert without a tested incident process: a consent framework built on voluntary agreement, no coercion, capacity, knowledge and autonomy, plus trauma‑informed response, confidentiality, timelines and escalation to a neutral body. Describes Kubernetes’ CoC committee process (k‑8s.dev/cocin), recommends Contributor Covenant 1.4 over 2.0, cites consent academy data that ~5% of harms are intentional, and urges training, liability coverage, staffed roles, and publishing transparency reports (e.g., kicking 25 spam bots).
AI-written summary · about
chapters (11)
- 0:00Start
- 3:29The Code of Conduct Committee for Kubernetes
- 7:05Language and Cultural Differences
- 10:35Restoring Their Autonomy
- 11:10A Code of Conduct Is Itself Not a Legal Document
- 15:53The Culture of an Organization Is Determined by the Worst Behavior Its Leaders Tolerate
- 16:18Fourth Point that a Code of Conduct Committee Must Enforce these Norms
- 17:40Three Types of Bodies in Large Open Source Communities That Do Need To Have Private Function
- 25:44Individual Safety
- 32:43Fund Training and Create Staff Roles
- 34:11Closing Thoughts
related talks
34mWhy We Need Codes of Conduct -- and Why They're Not Enough
13mDeconstructing the Code of Conduct
46mImplementing Diverse and Inclusive Codes of Conduct
42mPanel: Beyond Codes of Conduct: Igniting Diversity in Your Community
13mWhat is the Kubernetes Code of Conduct Committee and What is it Working On
26mLinux Code of Conduct
42mCodes of Conduct in Action - Evolving Best Practices for Incident Response
40mWhy You Should Adopt an Open Source Code of Conduct