Why You Should Adopt an Open Source Code of Conduct
summary
Open source projects face measurable toxicity: surveys show 15% experienced rudeness, roughly 25% witnessed name‑calling and over 10% witnessed serious incidents; contributor demographics skew male (~95% men in OSS), dropping minority representation to ~15%. Adopting a clear, prominent code like Contributor Covenant with concrete examples, reporting channels and enforcement reduces anonymity‑driven abuse, improves recruitment and retention, and is already used by Jakarta Ambassadors, Eclipse and other organizations.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:59Toxic behavior consequences
- 10:06Diversity and inclusion
- 16:23Code of conduct challenges
- 24:06How codes solve problems
- 28:00Adopting and enforcing
- 32:29Beyond open source
- 34:16Q&A
related talks
26mLinux Code of Conduct
18mOpen Open Source
48mJudging a book by its cover - how inclusive is your community?
13mDeconstructing the Code of Conduct
13mOpen Web, Open Source, Open Communities
21mOpen Source Isn't For Everyone, But It Could Be
12mOnline community and safety in software engineering
34mWhy We Need Codes of Conduct -- and Why They're Not Enough