Open Source Survival Guide
summary
Claim: documentation is the preeminent issue for open source and fixing READMEs and guides yields the biggest usability wins. Three concrete roles appear: maintainers collaborators consumers. Practical tools and tactics: add a CONTRIBUTING file, use RuboCop and automated builds, provide Docker/Vagrant dev setups, label issues for first-time contributors, run pull-request nights and pair-program (Screenhero Hangouts Skype). Examples: a user-group PR night and mentoring produce accepted docs and fewer tickets; writing long-form guides (React Redux book) proves effective.
AI-written summary · about
chapters (7)
- 0:00Introduction to open source
- 4:56Dreyfus model of skills
- 10:51The documentation challenge
- 17:53Contribution strategies
- 23:23Improving project onboarding
- 30:16Community and communication
- 34:14Managing self-deception
related talks
56mEffective Documentation: The Key to Open Source Growth
38mGuide to getting started in open source
35mThe Art of Documentation and Readme.md for Open Source Projects
29mThe Technical Writers Guide to Contributing to Open Source Projects
27mDesign Your Open Source Project
30mHow you write matters in open source
22mA beginner's guide to Open Source
47mPanel Discussion: A How-to Guide for Contributing to Open Source as an Employee
