BoF: The Power of Cohorts in Advancing Open Source Contribution
summary
Call for Code runs a global program that claims 400,000 participants across 179 nations and shows deployed solutions with over 250 sensors deployed and one project exceeding 1,000 app downloads. The team uses organized 4–12 week cohorts (enterprise, academic, event-based) with handbooks, deep‑dive videos, office hours and playbacks; cohorts produce UI updates, bug fixes, sandbox labs, data‑model corrections and CI/CD automation. Cohorts demand heavy upfront maintainer work but become repeatable and scale contributor onboarding.
AI-written summary · about
chapters (18)
- 0:00Start
- 3:56A Deployment Framework incubates Call for Code projects
- 4:43Call for Code Model
- 6:56Challenges in open source maintenance
- 9:45Call for Code at a glimpse
- 13:43Open Source Cohort
- 15:48Benefits to Enterprise
- 18:31Benefits to Open Source Community
- 19:33Organizing team
- 25:57Handbook
- 26:34Deep dive videos
- 27:22Free resources & certificates
- 28:09Background: Casual contributions
- 29:06Hacktoberfest Stats!
- 30:04Enterprise Engagement
- 31:44Tradeoffs
- 32:14Making the effort worth it!
- 33:39Tips
related talks
13mOpen Web, Open Source, Open Communities
40mBridging the Gap: Mentorship Programs for Your Open Source Journey
41mOpen source for good: the people and projects driving change
33mOpen Source Sustainability & Philanthropy: Building Contributor Communities
22mDaunting to Doable: How Institutions can encourage Open Source Contributions
32mFrom Classroom To Cloud: Bridging Academia and the Open Sou...
45mPanel Discussion: Open Source as a Second Language
33mIncluding People