An Introduction to Cloud Foundry Core Development - Jen Spinney & Luan Santos, SUSE
summary
Cloud Foundry core development uses a PMC-governed model with teams spread across four continents, eight countries, nine time zones. Contribution paths include a 6–12 week dojo that embeds newcomers as full team members; teams pair-program, use TDD and a visible CI pipeline, and assign roles like anchor. Work is tracked in Pivotal Tracker with features estimated on a 1,2,3,5,8 point scale to compute velocity. Remote pairing uses Screenhero / tmux and always-on video.
AI-written summary · about
chapters (23)
- 0:00Introduction to speakers
- 1:07Motivation behind talk
- 1:27Cloud Foundry history
- 2:10Runtime PMC overview
- 3:12Governance and contributions
- 4:16Dojo onboarding process
- 6:01Global distributed teams
- 7:08Team structure and roles
- 8:57Team hierarchy and collaboration
- 10:00Anchor role explained
- 11:45Pair programming model
- 13:11Pairing schedule and focus
- 14:15Benefits of pairing
- 14:35Test-driven development
- 15:20Continuous integration pipeline
- 16:23Daily stand-up meetings
- 17:31Pair rotation strategy
- 18:12Iteration planning meeting
- 19:39Story points and velocity
- 22:32Weekly retrospective
- 23:38Communication channels
- 24:22Contributing without dojo
- 25:32Remote pairing methods
related talks
31mThe Cloud Foundry Dojo Experience — How to Become a Contributor
19mKeynote: Confessions of a Cloud Foundry PaaS Product Owner: How to Create a Successful Devops Team
02mCloud Foundry
25mThe Essential Getting Started Guide to Cloud Foundry
17mKeynote: Cloud Foundry: The Open Community's Model Citizen
10mReinventing businesses with Chip Childers
27mLessons Learned from Corelogic's Year of Agile Development with Cloud Foundry
17mCloud Foundry & Heidelberg: Innovating Together