Lessons Learned from Cultivating Open Source Projects and Communities
summary
Describes concrete practices for growing projects: use GitHub for a social center but note Gerrit worked well in OpenStack; ship a vagrant file so newcomers can vagrant up a sandbox; write a one‑line scope in the README (Chef cookbooks example) and avoid the OpenStack big tent trap that doubled scope and churn. Corporately backed projects (IKS at IBM) bring paid contributors but require explicit trust and a handoff plan to let go when maintainers leave. weekly IRC/text meetings ensure inclusive coordination.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:25Tools versus culture
- 3:13Project scoping
- 6:00Personal vs corporate projects
- 7:49Empathy and inclusivity
- 9:58Celebrity risks
- 11:30Defeats in open source
- 12:59Successful practices
- 16:09Building trust
- 19:25Project succession
- 20:34Is open source worth it?
- 22:24Q&A
related talks
25mLessons Learned from Cultivating Open Source Projects and Communities
15mLessons Learned from Cultivating Open Source Projects and Communities
34mHow to Build Collaboration and Influence Open Source Projects
24mBuilding a Foundation for Open Collaboration
49mCommunities Over Code: How to Build a Successful Project
23mGrowing A Successful and Sustainable Project
21mWhy I love open source development & what I learned from K8s
40mHow to Open Source a Project and Possibly Not Fail While Trying