The Path to Open Source for the Traditional Enterprise
summary
A traditional insurer describes running hundreds of OSS libraries, running pilots that sometimes succeed and sometimes fail, and staging a global engineering summit with 200–600 on site and 1,000 hybrid participants to seed collaboration. Teams adopt an in-sourcing step, publish repos only after license and security checks, and use common templates, automation and conduct policies. The organization builds an open source program office, reports clearer hiring and research partnerships, and warns that open sourcing is not a silver bullet.
AI-written summary · about
chapters (11)
- 0:00Open source in enterprises
- 1:08Open source engagement scopes
- 3:12Personal journey discovery
- 5:17Engineering Summits community
- 9:12Change management adoption
- 12:21Risks of open sourcing
- 15:27Safe contributor spaces
- 17:57Open source talent retention
- 19:22Sponsorship needed
- 20:48Simplifying engineering processes
- 22:13Current journey future
related talks
20mThe Open Source Program Office: If It's Such a Good Idea, Why Haven't We Been Doing It?
28mGoverning Open Source in the Enterprise: OSPO Strategies for Innovation and Compliance
23mThe Open Source Journey of the Most Unlikely Participant
43mFostering an Open Source Culture
29mOpen Source and IP Departments: Risk Containment and Portfolio Management
40mHow to Open Source a Project and Possibly Not Fail While Trying
35mOpen Source as a Product: Strategies for Building and Scaling Successful Open Source..
28mThe five stages of corporate open source adoption