From laggard to open source power house

From laggard to open source powerhouse A transformative journey to successfully build a strong open source culture Tobie Langel (@tobie) Principal, UnlockOpen

The open source journey

Technology adoption lifecycle

Innovators 2.5%

Early adopters 13.5%

Early majority 34%

Late majority 34%

Laggards 16%

Consume 100%

The open source journey

Comply (use in products) 73%

Contribute 29%

Contribute 56%

Culture No data

Why build a strong open source culture?

Understanding

Understanding 1. Strategic benefits

Commoditize Your Complement Company Focus Complement

On-ramp developers

Understanding 2. Operational benefits

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

Economic Web browsers

Leverage external contributions React Router Redux React Ecosystem

Understanding 3. Second-order benefits

Problem Coffee Engineer Sarcasm (by-product) Solution

Problem Coffee Software Engineer Sarcasm (by-product) CODE

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

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

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

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

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

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

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

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.

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

“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.

How do you build a strong open source culture?

Facebook

outsized impact

clear overlap between internal and community priorities

Microsoft

.

Recap

Recap ● ● and ● ●

Recap ● ●

Open source isn’t a journey. It’s a practice.

but we should never be done. It’s a way of being.

Thank you. Tobie Langel (@tobie) Principal, UnlockOpen tobie@unlockopen.com unlockopen.com