Slide 1

Slide 1 text

1 #GitLabCommit Why Community Matters Tim Hockin Google Cloud

Slide 2

Slide 2 text

2 #GitLabCommit

Slide 3

Slide 3 text

3 #GitLabCommit

Slide 4

Slide 4 text

4 #GitLabCommit ● Started in 2013 ● Announced in 2014 ● 1.0 in 2015 ● Probably the largest Go project in the world ● One of the most active OSS projects in history Kubernetes

Slide 5

Slide 5 text

5 #GitLabCommit Oh, THAT kubernetes...

Slide 6

Slide 6 text

6 #GitLabCommit SPOILER ALERT!

Slide 7

Slide 7 text

7 #GitLabCommit This project WOULD NOT have become what it is today without the community In fact - it might not have been a success at all

Slide 8

Slide 8 text

8 #GitLabCommit You may have heard me or other Kubernetes people pontificate about community before That’s not going to stop me from doing it again today!

Slide 9

Slide 9 text

9 #GitLabCommit

Slide 10

Slide 10 text

10 #GitLabCommit “Coming together is a beginning. Keeping together is progress. Working together is success." --Henry Ford

Slide 11

Slide 11 text

11 #GitLabCommit This was probably the smartest thing Google did for Kubernetes It was not always easy, but it was worth it Radical Openness

Slide 12

Slide 12 text

12 #GitLabCommit

Slide 13

Slide 13 text

13 #GitLabCommit

Slide 14

Slide 14 text

14 #GitLabCommit Started accumulating contributors Mostly scratching their own itches Some were company sponsored Many just wanted to help, to be part of it 5+ years later - many are still with the project! The First Months

Slide 15

Slide 15 text

15 #GitLabCommit

Slide 16

Slide 16 text

16 #GitLabCommit

Slide 17

Slide 17 text

17 #GitLabCommit

Slide 18

Slide 18 text

18 #GitLabCommit v1.0 (1 year): ~500 contributors v1.4 (1 year later): > 1000 contributors Growth

Slide 19

Slide 19 text

19 #GitLabCommit Got a bunch of pull requests for ARM support Why? Unexpected

Slide 20

Slide 20 text

20 #GitLabCommit

Slide 21

Slide 21 text

21 #GitLabCommit Got a bunch of pull requests for ARM support Surprise #1: A Kube cluster of Raspberry Pi machines! Unexpected

Slide 22

Slide 22 text

22 #GitLabCommit Got a bunch of pull requests for ARM support Surprise #1: A Kube cluster of Raspberry Pi machines! Surprise #2: Contributor was 15 years old! Unexpected

Slide 23

Slide 23 text

23 #GitLabCommit Got a bunch of pull requests for ARM support Surprise #1: A Kube cluster of Raspberry Pi machines! Surprise #2: Contributor was 15 years old! We eventually made him a maintainer Unexpected

Slide 24

Slide 24 text

24 #GitLabCommit Got a bunch of pull requests for ARM support Surprise #1: A Kube cluster of Raspberry Pi machines! Surprise #2: Contributor was 15 years old! We eventually made him a maintainer Lesson: You NEVER KNOW where your community will come from Unexpected

Slide 25

Slide 25 text

25 #GitLabCommit

Slide 26

Slide 26 text

26 #GitLabCommit As a developer platform, docs are CRITICAL Software engineers wrote the first docs...yikes Do you know how hard it is to write, organize, and curate good technical docs? Docs

Slide 27

Slide 27 text

27 #GitLabCommit HARD HARD DOCS

Slide 28

Slide 28 text

28 #GitLabCommit We all know how important it is But we don’t always act that way Our testing SIG keeps us all sane Testing

Slide 29

Slide 29 text

29 #GitLabCommit We merge dozens to hundreds of PRs every day We cut a release every 3 months Our release team is community They have a robust shadowing program, too! Release Engineering

Slide 30

Slide 30 text

30 #GitLabCommit We have teams that runs our: ● GitHub ● Slack ● Website ● DNS ● Bots Heck, we even have a community-driven community management team!! Infrastructure

Slide 31

Slide 31 text

31 #GitLabCommit Now imagine Kubernetes without the community...

Slide 32

Slide 32 text

32 #GitLabCommit The project would not work.

Slide 33

Slide 33 text

33 #GitLabCommit The project would not work. At all.

Slide 34

Slide 34 text

34 #GitLabCommit It’s not just the people. It’s the stuff between the people. And it makes all the difference

Slide 35

Slide 35 text

35 #GitLabCommit