5/ GitHub Inner Source @ OPEN'16

How people build software

!

"

OPEN’16Lutger Kunst @lukeart


Inner Sourceadopting open source principlesto ship better code earlier & more often

2

♥

Lutger Kunst

Solutions Engineer

GitHub


!About us

3

FOUNDED

2008

GLOBAL RANK

#55

OFFICES

San Francisco Tokyo, Amsterdam, Boulder

USERS

15M

DAILY VISITORS

3M

REPOSITORIES

38M


gA brief history of GitHub

4

g

2 0 1 0 . C O R P O R A T E T E A M S

Usage expands to include

working groups and project

teams within corporations

2 0 1 2 . E N T E R P R I S E

Major enterprises begin to

leverage the GitHub approach

to software development

2 0 0 8 . S O C I A L C O D I N G

GitHub launches a social

software platform that makes it

easy for anyone to share code.


HappinessNo mockery in this world ever sounds to me so hollow as that of being told to cultivate happiness. What does such advice mean? Happiness is not a potato, to be planted in mould, and tilled with manure.

― Charlotte Brontë, Villette

5

$


Open Source DevelopmentThe development of open source software involves bringing a widely distributed group of people together to work on complex problems while primarily communicating online.

6

%


!2300% more requests served per second

7

!


Open source projects have constraints

8

&

GEOGRAPHY TIMEZONE CULTURE

'%

!


Open source principles

9

TRANSPARENCY PARTICIPATION COLLABORATION

( ) *

!


The medium and the message are transparent

10

+ ' )

ELECTRONIC ASYNCHRONOUS LOCK-FREE

!


The medium and the message are transparent

11

+ ' )

ELECTRONIC ASYNCHRONOUS LOCK-FREE

ARCHIVED,

!


Minimizing friction enables participation

12

- ) &

DOCUMENTATIONREADME.md

CONTRIBUTING.md

GITHUB FLOWMake it easy to

propose changes

AUTOMATIONAllows reviewers tofocus on substance


!Minimizing friction - Documentation

13


!Minimizing friction - GitHub Flow

14



15

Experimentation Without Risk

Branch — Question, Hypothesis, Experiment, Analyze,

Conclude

Pull Request — Gather feedback from peers and

integrate with 3rd party products to perform

automation for quality of code, build status, and

deployment



16

Pull Request feedback loop

Writing a Pull Request — Include the purposes and why

the work is taking place. Include any references. Be

explicit about when and what kind of feedback you want.

Use @mentions to bring people into the conversation.

Providing feedback — Make sure you understand the

context of the pull request and explain any code changes

you propose. Use positive language.

Responding to feedback — Express that you appreciate

their feedback. Ask for clarification if needed or clarify

why you made certain decisions. Try to respond to any

comment.


!Minimizing friction - Automation

17



18


!Apple Swift - Expanding Commit Access

19



20


!Code deploys - bring operations to the developer

21

+--------------------+ +--------+ +-----------------+ | GitHub Auto-Deploy | | GitHub | | Your Server | | Service | +--------+ +-----------------+ +--------------------+ | | | | | | Create Deployment | | |------------------------>| | | | | | | | | | Deployment Event | | |--------------------------------->| | | | | | Deployment Status (pending) | | |<---------------------------------| | | | | | | | | Deployment Status (success) | | |<---------------------------------| | | |


!Deploy on every push commit

22


!Deploy master on merge

23


!Use branch based deployments

24


!Deployment status

25


!Haystack exception tracking

26


!Code refactoring with Scientist

27

!


Put everyone in one spot with chat…

28

• Team rooms• Region based rooms• Social rooms• Private chat• Ops rooms


!… and bring your tools into your conversations

29


!Meet Hubot

30


!Hubot deploy example

31

!


Steps to create happy developers

32

• Ensure quality• Implement rigorous testing and build• Short-lived branches for small features• Make deploys boring and predictable• Require documentation in the

repositories• Require mature and respectful

behavior

• Improve collaboration • Let developers share their work• Require public and focused code

reviews• Give employees the confidence to

contribute code• Put everyone in one spot with chat• Share your experiences


!

"

Thank you!

5/ GitHub Inner Source @ OPEN'16

Software