Keeping Your Open Source Project Accessible to All
summary
Argues that concrete steps — not vague goodwill — increase contributions: use a measurable baseline (GitHub survey numbers showing roughly 95% male, 3% female, 1% non‑binary), fix broken READMEs and add glossaries, run mentorship programs that turn long PRs into hires (one maintainer spent a month annotating and mentoring), and add accessibility tools like the UserWay plugin; claims these actions boost diverse participation and gives OpenStack and replicated links as working examples.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:17Who am I
- 2:10Who am my copresenter
- 2:51Replication
- 3:29What we do
- 4:02We want more diversity
- 5:06Open Source Survey
- 5:39GitHub Survey
- 5:58I Lost
- 6:31Personality Conflict
- 8:59Documentation Tips
- 11:55Userway Plugin
- 12:45More Diversity
- 14:41Be Responsive
- 15:22Update Your Readme
- 16:06Dont Reject Without Reason
- 16:26John Murphy
- 17:54Diversity is our power
- 19:13Questions
related talks
38mKeeping Your Open Source Community Accessible to All
32mBuilding inclusive Open Source communities
21mOpen Source Isn't For Everyone, But It Could Be
23mHow to Demonstrate Allyship to Women+ in Open Source
11mOpen Source Standards: Toward a more diverse and equal internet
23mOpening Up The Current Open Source Blueprint
27mDesign Your Open Source Project
15mAdopting Open Source Practices To Build More Inclusive Products and Services