Talking with Management About Open Source
Provides talking with Management About Open Source and evaluates key implications for security practitioners.
Summary
### Overview In this talk, Rich Bowen, a member of the open source group at AWS and a long-time board member of the Apache Software Foundation, addresses the challenge of communicating the value of open source to corporate management. While individual contributors are often motivated by personal enjoyment, community connection, altruism, or resume building, businesses operate to generate profit, mitigate risk, and serve customers. Bowen provides actionable advice on how practitioners can reframe open source engagement from a personal hobby or moral obligation into strategic, business-aligned investments that leadership understands and supports.
### Key Topics - **Reframing Personal Motivations into Business Value**: Common practitioner motivations—such as altruism, socialization, and fun—do not resonate with executives. Practitioners must translate these drivers into business-critical concepts like supply chain sustainability, risk management, and talent retention. - **Avoiding Early Pitfalls in Management Conversations**: When initiating discussions with management, developers should avoid jumping into open source philosophy, nuanced licensing disputes, and technical jargon like "Upstream." Initial conversations should be brief, data-driven, and focused on commercial impact. - **Securing the Software Supply Chain**: Companies often rely heavily on open source components without contributing back, introducing severe operational risk. Contributing to critical projects is essential to ensure they remain funded, staffed, and viable over the long term. - **Building Trust, Influence, and Expertise**: Active participation allows companies to earn community trust, influence technical direction to align with customer needs, and develop in-house engineering expertise rather than treating open source as merely free software.
### Technical Details & Real-World Examples - **Security and Supply Chain Fragility**: Bowen highlights major security vulnerabilities such as Heartbleed, Meltdown, Spectre, and Log4Shell. These critical incidents illustrated the risk of multi-billion-dollar global supply chains relying on projects maintained by small, underfunded groups. Bowen notes that these incidents were resolved faster due to open source collaboration, but they emphasize the danger of companies not actively supporting dependencies. - **Single-Vendor and Single-Maintainer Risks**: Projects governed by a single vendor risk sudden license changes or abandonment if corporate priorities shift. Single-maintainer projects present even higher operational risk. Bowen notes real-world disruptions, including the impact of the war in Ukraine on local open source maintainers whose projects required intervention to survive. - **Undifferentiated Heavy Lifting**: Drawing on Amazon's concept of "undifferentiated heavy lifting," Bowen explains that commodity open source software should be collaboratively maintained with the broader community, freeing companies to focus resources on their unique competitive differentiators (e.g., cloud scale for AWS, silicon architecture for Intel). - **The True Cost of "Free"**: Open source is "free as in puppies" rather than free as in cost. It requires ongoing investment in developer time, upstream maintenance, and community engagement to prevent the technical debt and maintenance burden associated with internal forks.
### Takeaways - **Speak the Language of Business**: Anchor conversations in data, profit impact, risk management, and customer pain points rather than moral obligation or charity. - **Treat Open Source as a Long-Term Investment**: Gaining trust, upstreaming patches, and steering project roadmaps require patience—often taking two to three years to realize concrete returns. - **Respect Community Social Norms**: Avoid aggressive corporate posturing, claiming sole ownership of shared tools, or overpromising rapid control to executive leadership. - **Support Strategic Dependencies**: Identify strategic open source dependencies and invest engineering resources and funding to ensure they remain robust and sustainable.
Related talks
The Linux Foundation·41 min
Tom Callaway
Provides talking with Management About Open Source and evaluates key implications for security practitioners.
The Linux Foundation·38 min
Nikola N · Marcel K · Takashi N · Ayumi W · Helio C
Demonstrates panel: Open Source Management Based on Open Source and evaluates key implications for security practitioners.
The Linux Foundation·42 min
Ana Santamaría · Daniel Cortázar
Provides the Role of Open Source Management Talent in Ensuring Software and evaluates key implications for security practitioners.


