Implementing Diverse and Inclusive Codes of Conduct
summary
Codes of conduct serve to protect marginalized members by naming scope, unacceptable behaviours, consequences and a reporting process that lists specific responders; recommended safety teams are 3-6 people with staggered turnover and named contacts, timelines include announce within three hours and aim to resolve incidents in days, responses use pre-approved actions and avoid mediation or forced apologies, maintain incident records and publish outcomes, and adoptables include the Contributor Covenant (~44,000 users) as a concise baseline.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 0:58Who am I
- 1:19Reconciliation
- 1:36Matthews background
- 2:03Overview
- 3:14Code of Conduct
- 6:52How does a Code of Conduct work
- 8:14Deterrence
- 8:55Limits
- 11:50Summary
- 12:29Application
- 12:42Publish
- 13:34Safety Team
- 15:50Communication
- 20:22Response
- 29:07Response Summary
- 30:05Popular Codes of Conduct
- 31:10Unacceptable Behavior
- 32:18Contributor Covenant
- 32:42Community Impact Guidelines
- 33:59Conclusion
- 34:24References
- 35:39Questions
- 40:22Recommendations
- 42:20When to report
- 44:33Optimal level of complexity
related talks
13mDeconstructing the Code of Conduct
42mCodes of Conduct in Action - Evolving Best Practices for Incident Response
44mWhy We Need Codes of Conduct, and Why They're Not Enough
34mWhy We Need Codes of Conduct -- and Why They're Not Enough
23mEnforcing Your Code of Conduct: Effective Incident Response
26mLinux Code of Conduct
13mBuilding an Inclusive, Diverse Community From the Ground Up
40mWhy You Should Adopt an Open Source Code of Conduct