Lessons Learned from Cultivating Open Source Projects and Communities
summary
Describes concrete practices: use of Gerrit then GitHub, corporate-backed projects (IBM IKS) vs personal scoping, and the danger of OpenStack’s big tent swallowing focus. Recommends reproducible local dev with a vagrant up sandbox that pulls and builds the code, enforces a single-line README scope line to stop cookbook bloat, and runs weekly IRC meetings to surface non-native-English contributors. Warns that public “celebrity” awards create caste effects, and emphasizes trust and an exit/ownership handoff plan.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:14This isn't a tools talk
- 1:56Scoping your Project
- 4:21Personally-backed
- 5:56Corporate-backed
- 6:56Empathy and Audience is Important
- 8:46Celebrations
- 10:42Defeats
- 12:54Successful traits of Open Source Projects
- 15:58Trust
- 17:45Clear Vision
- 19:31A Plan to Move on
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
49mCommunities Over Code: How to Build a Successful Project
36mThe Feedback Loop: Growing healthy open source projects
27mDesign Your Open Source Project
24mBuilding a Foundation for Open Collaboration
21mLeading and Growing an Open Source Comunity