Including People
summary
An open source project uses explicit codes of conduct, layered documentation (tutorials, topic guides, API reference, troubleshooting) and scheduled pairing sessions to turn strangers into contributors; a published troubleshooting checklist resolves 60–70% of problems before opening issues. The claim is that documenting contributor setup, triage steps and release procedures and enforcing conduct actually increases participation; concrete practices include triage scripts, onboarding docs, pairing hours and measurable reductions in support load.
AI-written summary · about
chapters (22)
- 0:00Intro
- 4:06About this talk
- 5:23Background
- 6:55Diversity
- 7:43Inclusion
- 8:25Bias
- 10:57The Problem
- 13:53Attitude
- 14:29Open Source
- 15:06Linux
- 16:14Code of Conduct
- 17:16Documentation
- 18:48Four types of documentation
- 21:16Issue reports
- 24:12Follow the code
- 25:43Ask for help
- 28:09Development documentation
- 29:35Pull requests
- 31:17Respect Empathy
- 31:38Respect Others
- 32:07Call Out Problems
- 32:30Change Text
related talks
42mBuilding On-Ramps for Non-Code Contributors in Open Source
18mOpen Open Source
13mOpen Web, Open Source, Open Communities
20mOpen up to Open Source
20mHumans of Open Source
44mBuilding On-Ramps for Non-Code Contributors in Open Source
38mHow to bring open source to a closed community
18mOpen communication for open development
