How you write matters in open source
summary
Argues that open source spends as much time on written communication as on code and gives concrete fixes: adopt an existing style guide (Bottle Rocket uses the OpenStack guide), run linters for inclusive terms, publish a glossary and use footnotes and links, and define antecedents instead of ambiguous we statements. Diagnoses common errors—anthropomorphism (projects “say” things), overloaded terms like “support”—and shows practical examples (blog release phrasing, issue 467, PR feedback) and how automation plus clearer phrasing reduces confusion.
AI-written summary · about
chapters (6)
- 0:00Introduction to writing in open source
- 3:34Writing effort in open source
- 7:51Overarching ideas for writing
- 15:15Practical lessons learned
- 22:16Key takeaways and summary
- 23:19Q&A session
related talks
50mOpen Source Survival Guide
56mEffective Documentation: The Key to Open Source Growth
34mThe 10 Biggest Mistakes You Shouldn’t Make In Open Source
16mThere's More to Open Source than Code
29mThe Technical Writers Guide to Contributing to Open Source Projects
23mKeeping Your Open Source Project Accessible to All
27mDesign Your Open Source Project
25mThere's More to Open Source than Code