Why We Need Codes of Conduct -- and Why They're Not Enough
summary
Open source projects need operational practice, not just a document: Kubernetes' committee publishes a process using the four pillars of consent (autonomy, capacity, information, negotiated boundaries) plus trauma‑informed intake, clear timelines, confidentiality rules, and escalation paths. Concrete recommendations include shifting from punishment to support, publish transparency reports to show outcomes without breaching privacy, fund training and liability coverage for volunteers, and prepare for legal risk — there are three lawsuits (as of 2022) tied to code enforcement.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:17Why We Need Codes of Conduct
- 3:51Capacity
- 5:46Set Clear Expectations
- 7:15Codes of Conduct Are Not Laws
- 8:22A Code of Conduct Should Not Center Punishment
- 31:38Recap
- 32:37Closing Thoughts
related talks
44mWhy We Need Codes of Conduct, and Why They're Not Enough
46mImplementing Diverse and Inclusive Codes of Conduct
26mLinux Code of Conduct
13mDeconstructing the Code of Conduct
42mPanel: Beyond Codes of Conduct: Igniting Diversity in Your Community
18mOpen Open Source
40mWhy You Should Adopt an Open Source Code of Conduct
33mIncluding People