Achieving the Tipping Point for Open-source Software: Making the Business Value Obvi...
summary
Provides a concrete four-question framework to justify OSS: tie the project to company goals, state the exact outcome, list design principles, and document alternatives and due diligence. Uses metrics (KubeCon growth from ~500 to 12,000; OSS contributions +25% year over year; 40% more GitHub projects at lockdown) and recommends tools like CNCF DevStats and stream processors (e.g., Flink) to show you can reduce mean time to detection from >10 minutes to seconds, de-risking OSS for management.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:11Takeaways
- 4:21Law of the Few
- 4:37Stickiness Factor
- 4:55What Is the Open Source Movement
- 7:07Timing
- 12:53Did I Truly Do Due Diligence
- 13:25Example One Reducing Mean Time to Detection
- 14:25The Design Principles
- 15:24Refactor Project
- 17:28Building Multi-Cloud Sas
- 18:03Design Principles
- 18:55Third-Party Abstractions
- 22:03Growing Your Professional Brand
related talks
38mOpen-Source - Open Choice: A DevOps Guide for OSS Adoption
28mOpen Source: Open Choice – A DevOps Guide for OSS Adoption
34mConsumers To Contributors: Open Source As a Competitive Advantage
40mHow Can Your OSPO Drive Open Source Business Value for Your Organization?
35mHow Can Your Organization Maximize Open Source Business Value?
29mOpen-Source: Open Choice - A DevOps Guide for OSS Adoption
23mMaking the Business Case for Contributing to Open Source
13mWelcome