Judging a book by its cover - how inclusive is your community?
summary
Open-source communities lose contributors to tone and friction: a 2017 GitHub survey shows 18% experience negative interactions, 50% witness them, 21% stop contributing, over 50% encounter dismissive replies and 93% see missing documentation. Practical fixes: adopt a prominent code of conduct and anti-harassment rules, publish governance and leadership makeup, fund accessible events (scholarships that don’t reimburse), make contribution paths obvious, and invest in mentorship and documentation, clear social media/comment policies, and weed out toxic unofficial leaders.
AI-written summary · about
chapters (10)
- 0:00Inclusive open source intro
- 5:23Traits of welcoming communities
- 10:00Leadership diversity impact
- 15:00Inclusive events and speakers
- 21:24Simpler contribution paths
- 24:45Mentorship and docs growth
- 27:58Accessibility beyond tech
- 30:46Case studies in open source
- 39:56Drupal inclusion efforts
- 44:03Kindness vs realistic expectations
related talks
40mJudging a book by its cover - how inclusive is your community?
40mWhy You Should Adopt an Open Source Code of Conduct
32mBuilding inclusive Open Source communities
13mBuilding an Inclusive, Diverse Community From the Ground Up
23mKeeping Your Open Source Project Accessible to All
38mKeeping Your Open Source Community Accessible to All
18mOpen Open Source
21mOpen Source Isn't For Everyone, But It Could Be