From 0 to core contributor
summary
Dojo converts newcomers into core committers through 6–8 weeks of enforced pair programming, TDD-first development and team rotation, aiming for 100% test coverage. Remote pairing uses Screenhero, Google Hangouts and Slack to keep pairs productive; reported outcome is faster onboarding and fewer regressions. Core access is awarded at program end and the dojo is free; a notable outlier became a committer by rewriting the DEA in Go and shipping it fully tested, proving the process scales to major contributions.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:29Topics
- 2:00Who are you
- 2:49What is it really
- 3:26Benefits
- 6:00TDD
- 12:25Dojo Program
- 13:42Pairs
- 15:17Current EDD
- 16:40Crowd
- 17:55IPM
- 19:26Team rotation
- 20:45Pairing
- 21:21Team Accessibility
- 21:43Slack
related talks
31mThe Cloud Foundry Dojo Experience — How to Become a Contributor
33mThe Pivotal Engineering Dojo
46mLearning That Sticks - Upskill Your Teams with a Dojo
49mDo you wanna be a core dev? (You don't have to be core dev...)
36mDojo: An Effective Implementation to Improve TDD Practice
18mOpen communication for open development
28mAn Introduction to Cloud Foundry Core Development - Jen Spinney & Luan Santos, SUSE
15mThe Open Source Community Core