Fostering Diversity in Open Source Communities
summary
A well established ML‑family programming language community adopts a code of conduct after two attempts (initial 2017 effort, relaunch in 2022), formed enforcement team with bylaws to avoid conflicts of interest, and applies the policy to core channels (GitHub Discord mailing lists) with clear escalation steps from private to public escalation to apology and bans; the process reuses vetted text (used Contributor Covenant), responds to a 2017 survey finding 3% women and 16% ethnic minorities, and evolves through community feedback rather than a one‑time rollout.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:10Code of conduct importance
- 2:33Diversity statistics
- 3:36Who can advocate for a code of conduct
- 4:22OCaml community intro
- 5:442017 CoC first attempt
- 6:27Second attempt and team
- 7:49Good enforcement team
- 9:59Bylaws and conflicts
- 10:42Violation steps
- 11:46When and how to adopt a code of conduct
- 12:47Debunking CoC concerns
- 14:14Power dynamics in enforcement
- 14:55Amendments and finalizing the code of conduct
- 15:17Key takeaways
- 15:38Q&A
related talks
29mExperiences in Addressing Diversity, Equity, and Inclusion in Open Source Governance
26mLinux Code of Conduct
40mWhy You Should Adopt an Open Source Code of Conduct
27mWhy Open Source Fails to Protect Under-Represented Minorities
30mTokenism in Open Source: Diversity or Decoration?
42mPanel: Beyond Codes of Conduct: Igniting Diversity in Your Community
31mHow to amplify diversity inside a Python community?
18mOpen Open Source