Design Your Open Source Project
summary
Argues that open source delivers concrete benefits: collaboration and external validation, with GitHub-style workflows and numbers — a workplace opens 85-90% of its work and a library like Resque attracts 135 contributors — not fluff. Recommends specific tools and practices: use Travis c.org for CI, write a clear README and docstrings, host docs on Read the Docs / Sphinx, pick a license to match the contribution model, plan for support and an exit strategy, and build a small usable project (Dango image kit style) and verify it actually gets contributions.
AI-written summary · about
chapters (8)
- 0:00Open source beyond code
- 4:56Project purpose first
- 7:00Methodologies and licenses
- 9:08Documentation that shines
- 12:20Promoting projects
- 16:35Motivation for students
- 19:08Introduction
- 22:17Q&A
related talks
56mEffective Documentation: The Key to Open Source Growth
01h 03mThe Value of Open Source
38mGuide to getting started in open source
23mKeeping Your Open Source Project Accessible to All
16mThere's More to Open Source than Code
23mGrowing A Successful and Sustainable Project
28mBest Practices for an Effective Open Source Contribution
18mOpen Source Like A BOSS