Zero to Opensource Hero: A Journey to Enable a Culture Based on Open Source Contribu...
summary
Fidelity embeds open source contribution into developer experience and reports a three‑month pilot: three months that proves the model, then scales via nano contributions 1–2 hours tied to weekly learning days and measures success by contributors and contributions only. Mini‑jams with 10–12 people boost pull‑through and contribution rates. Project clusters use federated steering groups of about three to four to grow active contributors. A concrete win: a several‑line Helm chart change removes repeated manual toil from a weekly release pipeline.
AI-written summary · about
chapters (17)
- 0:00Open source contribution journey
- 1:03Why start open source contributions
- 2:50Small pilot program start
- 4:57Three-tier contribution strategy
- 7:24Strategy with steering groups
- 8:51Measuring Nano contributions
- 10:15Nano contributions challenges
- 12:02Expertise via project clusters
- 13:31Scaling with micro steering groups
- 14:38Organizational support key points
- 16:03Advocates driving change
- 17:07Contributions in learning paths
- 18:09Upstream-first mindset shift
- 19:31Embedding contributions in backlogs
- 20:57Upstream challenges
- 21:39Summary
- 22:03Q&A
related talks
41mSteady and Deliberate: Enabling Contributions in a Regulated Industry
23mThe Open Source Journey of the Most Unlikely Participant
38mHow to bring open source to a closed community
52mBottom-Up Open Source Culture
18mOpen communication for open development
27mOpen Source: Supporting, Contributing and Evangelising
43mFostering an Open Source Culture
13mHow can we truly arrive at "open-source everywhere"?