Keeping Your Open Source Community Accessible to All
summary
GitHub 2017 data shows 95% male contributors versus BLS data with ~23% female programmers and ~34% people of color, highlighting a gap. Concrete fixes: prioritize responding to PRs within 24–48 hours, add clear quickstarts, a project-specific glossary, and accessibility plugins like UserWay. Create a maintainer/mentor list (RDO-style), treat every PR as teachable—one careful review can turn a contributor into a hire—and stop using exclusionary terms.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:28Keeping Your Open Source Projects Accessible to All
- 3:04Why We'Re Here
- 8:33Bad Documentation
- 10:46Create a Glossary
- 15:02Be Responsive
- 18:51Q a Time
- 36:24Do Corporations Have Responsibilities
related talks
23mKeeping Your Open Source Project Accessible to All
55mDiversity in OpenSource … show me the data!
32mBuilding inclusive Open Source communities
30mCommit to Inclusion: Building Better Open Source Culture
21mOpen Source Isn't For Everyone, But It Could Be
23mOpening Up The Current Open Source Blueprint
39mThe Gender Gap in Open Source is a Metadata Problem (and we can fix it)
07mDiversity in Open Source