Making the Business Case for Contributing to Open Source

A presentation at All Things Open 2019 in October 2019 in Raleigh, NC, USA by Tobie Langel

Slide 1

Slide 1

Making the business case for contributing to open source Photo: Dix campus, 2012 (CC BY 2.0) Tobie Langel (@tobie) Principal, UnlockOpen

Slide 2

Slide 2

“In short, software is eating the world.” open source —Marc Andreessen, WSJ, August 20, 2011. 96% 57% OF APPS CONTAIN OPEN SOURCE COMPONENTS OF CODEBASE IS OPEN SOURCE Source: Black Duck 2018 OSSRA

Slide 3

Slide 3

And yet…

Slide 4

Slide 4

…few companies contribute back.

Slide 5

Slide 5

Why should companies contribute to open source? Common good The Right Thing To Do™ Paying it forward Etc.

Slide 6

Slide 6

The Right Thing To Do™ Paying it forward Common good

Slide 7

Slide 7

Lack know-how The Right Thing To Do™ Paying it forward Increased Risk Wasted resources Common good Lost IP Lost competitive advantage

Slide 8

Slide 8

The ROI of using open source is well understood. The ROI of contributing to open source: not so much.

Slide 9

Slide 9

The risk of contributing to open source is: • not well understood, • generally exaggerated.

Slide 10

Slide 10

Understanding the value of contributing to open source 1. Strategic benefits 2. Operational benefits 3. Second-order benefits

Slide 11

Slide 11

Understanding the value of contributing to open source 1. Strategic benefits 2. Operational benefits 3. Second-order benefits

Slide 12

Slide 12

Commoditize Your Complement Company Focus Complement

Slide 13

Slide 13

On-ramp developers

Slide 14

Slide 14

Understanding the value of contributing to open source 1. Strategic benefits 2. Operational benefits 3. Second-order benefits

Slide 15

Slide 15

Photo: Pablo Andrés Rivero, 1997 (CC BY-NC-ND 2.0) Payback Technical Debt

Slide 16

Slide 16

Economic Web browsers

Slide 17

Slide 17

Leverage external contributions React Router Redux React Ecosystem

Slide 18

Slide 18

Understanding the value of contributing to open source 1. Strategic benefits 2. Operational benefits 3. Second-order benefits

Slide 19

Slide 19

Problem Coffee Engineer Sarcasm (by-product) Solution

Slide 20

Slide 20

Problem Coffee Software Engineer Sarcasm (by-product) CODE

Slide 21

Slide 21

Problem Coffee Software Engineer Sarcasm (by-product) CODE Commons

Slide 22

Slide 22

Problem Coffee Software Engineer Sarcasm (by-product) Commons OPEN SOURCE CODE Conversations Code reviews Mentoring Networking Etc. Software Engineer Sarcasm (by-product) Problem Coffee

Slide 23

Slide 23

Problem Coffee Commons Software Engineer OPEN SOURCE CODE Conversations Code reviews Mentoring Networking Etc. Sarcasm (by-product) Adopt best-prac tices Increase code qua BY-PRODUCTS Software Engineer Problem Coffee Sarcasm (by-product) & morale e r u lt cu d e v o pr Im Improve soft-skills Lower technical debt Improve documentation Reduced churn Remote friendly Innovation Influence project directio Increase effi n ciencies Access to talent pool ry leader t s u d in s a d e iv Perce Level-up engineers y t i p i d Access to expert n “Knowledge spillover” Seren Better career opportunities etwork lity

Slide 24

Slide 24

BY-PRODUCTS PROJECT INDIVIDUAL TEAM ORGANIZATION Improve documentation Level-up engineers Increase efficiencies Improved culture & morale Increase code quality Adopt best-practices Serendipity Perceived as industry leader Lower technical debt Improve soft-skills Innovation Access to talent pool Influence project direction Access to expert network “Knowledge spillover” Remote friendly Better career opportunities Reduced churn

Slide 25

Slide 25

2× TWICE AS EFFICIENT Contributing firms capture up to 100% more productive value from usage of open source than their free-riding peers. Source: Franck Nagle, Learning by Contributing, 2017.

Slide 26

Slide 26

75% 75% of facebook’s new engineering recruits mention facebook’s open source program as a key reason they accepted their offer

Slide 27

Slide 27

“But we also noticed some effect that we didn’t expect. All the public visibility [sponsoring Webpack] have given us lead to a situation where we suddenly became one of the most interesting companies to work for as a JavaScript developer. […]” “We’ve hired a lot of really great engineers who mentioned during their job interview that our sponsoring for Webpack was one of their primary motivations for applying, […]” —Patrick Gotthardt, Lead JavaScript Architect, Trivago, 9 July 2018.

Slide 28

Slide 28

Lack know-how The Right Thing To Do™ Paying it forward Increased Risk Wasted resources Common good Lost IP Lost competitive advantage

Slide 29

Slide 29

Lack know-how Increased Risk Lost IP Wasted resources Lost competitive advantage

Slide 30

Slide 30

Mitigate the risk of contributing to open source

Slide 31

Slide 31

Lost competitive advantage “I skate to where the puck is going to be, not to where it has been.” —Wayne Gretzky Photo: Rick Dikeman, 1997 (CC BY-SA 3.0)

Slide 32

Slide 32

Photo: O’Reilly AI Conference, 2016 (CC BY-NC 2.0) Lost IP “In today’s world of fast-paced internet services deployment, owning IP has become considerably less important than turning research results into innovative products as quickly as possible, and deploying them at scale.” —Yann LeCun, Business Insider, Aug. 3, 2018.

Slide 33

Slide 33

Increased Risk Wasted resources Lack know-how Etc.

Slide 34

Slide 34

Slide 35

Slide 35

Slide 36

Slide 36

Now it’s your turn!

Slide 37

Slide 37

Now it’s your turn! • Framework to think in terms of business tradeoffs. • A toolkit of benefits and mitigation strategies. • See how it applies to your organization.

Slide 38

Slide 38

Now it’s your turn! • Be reasonable. • Show empathy to others’ needs in the organization. • Aim for small wins. Start small. • Remember it’s a mindset shift.

Slide 39

Slide 39

Photo: Bill Dickinson, 2015 (CC BY-NC 2.0) Thank you! Tobie Langel Principal, UnlockOpen tobie@unlockopen.com unlockopen.com