The Cloud Foundry Dojo Experience — How to Become a Contributor
summary
Cloud Foundry Dojo runs on a six to ten week on‑site immersion that starts with a one‑hour remote pairing interview and aims to make participants committers within that period. Work happens as pair programming all day, rotating partners, owning a scoped team area and shipping through Concourse CI pipelines that run component tests then BOSH acceptance tests. Typical tooling includes Git (workarounds for dual authorship), RubyMine, Vagrant and the Linux CLI; an outcome example is contributing to BOSH OpenStack CPI and becoming a committer, with a one‑year participation expectation and travel cost.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:45What is the Dojo
- 1:23The Dojo journey
- 3:59Pairing
- 5:43Plato and Socrates
- 11:59Rhythm of life
- 13:31After the Dojo
- 16:03CI Pipelines
- 18:10tooling
- 20:39learning
- 24:04challenges
- 27:02tips
related talks
33mThe Pivotal Engineering Dojo
30mFrom 0 to core contributor
28mAn Introduction to Cloud Foundry Core Development - Jen Spinney & Luan Santos, SUSE
30mContinuous Delivery to Cloud Foundry: Why Your Junior Devs Will Love It! - Robert Summers, Armakuni
07mMy Path to Cloud Foundry Approver
16m6 Months In: A User’s Journey into the Foundation
10mCloud Foundry Accelerates "DevOps+"
46mLearning That Sticks - Upskill Your Teams with a Dojo