How the OCaml Community Established Its Code of Conduct
summary
Open-source OCaml adds a formal Code of Conduct added in 2022 after a multi-year effort starting around 2017: a volunteer adjudication team (five then six members, unpaid, rotated) drafts a document, solicits community feedback, and makes amendments; the final text originates from Contributor Covenant then switches to the COP/Rock template to avoid politicized wording; scope is limited to official OCaml spaces and maintainers handle reports through the volunteer committee.
AI-written summary · about
chapters (17)
- 0:00OCaml Code of Conduct intro
- 2:14OCaml ecosystem history
- 3:19What is a Code of Conduct
- 4:01Why projects need CoC
- 5:33OCaml CoC journey begins
- 7:21Forming the CoC team
- 9:09Volunteer-led challenges
- 10:55Team member expectations
- 12:22Team composition rotation
- 13:29Choosing CoC template
- 14:36Key CoC text elements
- 16:02Community feedback revisions
- 17:24Concerns about Contributor Covenant
- 19:53Finalizing OCaml CoC
- 20:38Clarifying CoC scope
- 20:58Acknowledgments group effort
- 22:20Q&A on community reactions
related talks
26mLinux Code of Conduct
17mFostering Diversity in Open Source Communities
44mWhy We Need Codes of Conduct, and Why They're Not Enough
40mWhy You Should Adopt an Open Source Code of Conduct
18mOpen Open Source
34mWhy We Need Codes of Conduct -- and Why They're Not Enough
13mDeconstructing the Code of Conduct
46mImplementing Diverse and Inclusive Codes of Conduct
