From laggard to open source powerhouse A transformative journey to successfully build a strong open source culture Tobie Langel (@tobie) Principal, UnlockOpen
Slide 1
Slide 2
The open source journey
Slide 3
The open source journey
Slide 4
The open source journey
Slide 5
Technology adoption lifecycle
Slide 6
Innovators 2.5%
Slide 7
Early adopters 13.5%
Slide 8
Early majority 34%
Slide 9
Late majority 34%
Slide 10
Laggards 16%
Slide 11
Consume 100%
Slide 12
The open source journey
Slide 13
The open source journey
Slide 14
Comply (use in products) 73%
Slide 15
Contribute 29%
Slide 16
Contribute 56%
Slide 17
Culture No data
Slide 18
Why build a strong open source culture?
Slide 19
Why build a strong open source culture?
Slide 20
Understanding
Slide 21
Understanding 1. Strategic benefits
Slide 22
Commoditize Your Complement Company Focus Complement
Slide 23
On-ramp developers
Slide 24
Understanding 2. Operational benefits
Slide 25
Photo: Pablo Andrés Rivero, 1997 (CC BY-NC-ND 2.0) Payback Technical Debt
Slide 26
Economic Web browsers
Slide 27
Leverage external contributions React Router Redux React Ecosystem
Slide 28
Understanding 3. Second-order benefits
Slide 29
Problem Coffee Engineer Sarcasm (by-product) Solution
Slide 30
Problem Coffee Software Engineer Sarcasm (by-product) CODE
Slide 31
Problem Coffee Software Engineer Sarcasm (by-product) CODE
Slide 32
Problem Coffee Software Engineer Sarcasm (by-product) CODE Commons
Slide 33
Problem Coffee Software Engineer Sarcasm (by-product) Commons OPEN SOURCE CODE
Slide 34
Problem Coffee Software Engineer Sarcasm (by-product) Commons OPEN SOURCE CODE Software Engineer Sarcasm (by-product) Problem Coffee
Slide 35
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 36
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
Slide 37
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 38
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 39
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 40
75% 75% of facebook’s new engineering recruits mention facebook’s open source program as a key reason they accepted their offer
Slide 41
“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 42
How do you build a strong open source culture?
Slide 43
Slide 44
Slide 45
Slide 46
Slide 47
Slide 48
Slide 49
Slide 50
Slide 51
Slide 52
Slide 53
outsized impact
Slide 54
clear overlap between internal and community priorities
Slide 55
Slide 56
Microsoft
Slide 57
Slide 58
Slide 59
Slide 60
.
Slide 61
Slide 62
Slide 63
Slide 64
Slide 65
Slide 66
Recap
Slide 67
Recap ● ● and ● ●
Slide 68
Recap ● ●
Slide 69
Open source isn’t a journey. It’s a practice.
Slide 70
but we should never be done. It’s a way of being.
Slide 71
Thank you. Tobie Langel (@tobie) Principal, UnlockOpen tobie@unlockopen.com unlockopen.com
