Partnerships in Open Source - the friends you didn't know you had
summary
Capital One describes a five year open source first transformation: launched an OSPO in 2015, runs CI/CD at 10+ releases a day for some apps, and maintains ~20 public repos with thousands of external contributions. Notable outcomes include Cloud Custodian donated to CNCF and long‑running Hygieia metrics adoption. Practical tools built include a CLI precommit scanner pilot that checks sensitive data license and contribution issues before commit. Legal, risk, and brand integration, a 2018 cross‑company consortium, and contribution metrics drive whether projects scale or retire.
AI-written summary · about
chapters (18)
- 0:00Open source at a large financial institution
- 2:00Our Journey
- 4:52Our Featured Open Source Products
- 5:39Where do our partners step in?
- 9:28The role of an Open Source Program Office (OSPO)
- 11:32Establish open source-like culture
- 14:42Maintain continual compliance reviews and oversight
- 16:52Understanding the risks is key while evaluating your Open Source pre
- 22:03Engage with developer communities to contribute back
- 24:42Launch new open source projects
- 26:13What Do We Want To Avoid?
- 29:00What Is The Real Intent of The Project?
- 30:25Engaging stakeholders in our sponsorship process
- 33:50The impact of having the right people in the room
- 34:17The fruits of good preparation and oversight
- 35:30Where we engage in the software community
- 36:06Benefits of community engagement
- 37:06Key takeaways to a successful Open Source
related talks
44mOpen Source in Financial Services: The Good, The Bad and the Ugly
41mHow Your Company Can Help Sustain Open Source
27mOpen Source: Supporting, Contributing and Evangelising
35mOpen Source as a Product: Strategies for Building and Scaling Successful Open Source..
43mFostering an Open Source Culture
28mGoverning Open Source in the Enterprise: OSPO Strategies for Innovation and Compliance
23mThe Open Source Journey of the Most Unlikely Participant
13mWelcome