emc world 2016 - code.10 jumpstart your open source presence through new collaboration tools

1© Copyright 2016 EMC Corporation. All rights reserved. 1© Copyright 2016 EMC Corporation. All rights reserved.

JUMPSTART YOUR OPEN SOURCE PRESENCE WITH NEW COLLAB TOOLSDREW SMITH, EMC {code}MIKE FILOSA, GITHUB

3© Copyright 2016 EMC Corporation. All rights reserved.

• EMC {code} developer advocate• Systems Engineer for 18+ years• Lead SysAdmin for ISPs, games,

stock market, media firms• AWS / cloud early-adopter• Recovering OpenStack devotee• Still excited about open source!• Twitter: @mux

WHO IS DREW?


• GitHub Enterprise Solution Engineer • Works with enterprise customers

across the US (Including EMC)• Devops advocate and experienced

developer for 20+ Years• GitHub.com/mfilosa

WHO IS MIKE?


WHAT IS AN OPEN SOURCE STRATEGYAND WHY SHOULD YOU CARE


THE GAME IS CHANGING


• Where and how open source technologies should be used

• The process for evaluating, approving and governing open source components

• How to support and maintain the code• When and how an organization should work with

open source communities

AN OPEN SOURCE STRATEGY DEFINES:


• Cost savings on software licensing

• Increased technical/software velocity

• Better employee recruitment and retention

• Harness creativity and collaboration

YOU SHOULD CARE BECAUSE:


WHO IS USING OPEN SOURCE?


• Software development teams• Server/Internet operations teams• Internal IT• Sales/Marketing

WHAT THIS CAN LOOK LIKE


• Software is no longer just a budget item• Support is not guaranteed• Get involved!

– Take part in community conversations– Exchange ideas and concepts– Contribute knowledge or code

YOUR PRESENCE IN OPEN SOURCE


• Users can interact directly with developers• Communication used to be done through Usenet• Also through Email ‘listserv’ discussion lists

– Good: archived and searchable– Bad: non-realtime interaction

OPEN SOURCE COMMUNITIES


• People are still using email listservs– Ubiquitous access across the world– Everyone knows how to use it– Email is not going away any time soon– …but post counts on many mailing lists are falling

STATUS IN 2016


• Larger communities gather for in-person Meetups– Though this

• Also often use IRC for real time interaction

OPEN SOURCE COMMUNITIES


• Old idea, still ticking• Text-mode chat• Can be open to the public or private

– Not archived, not searchable• Fills a hole between meetings and email

– Easy/quick interactions for your teams– Great place to build a community around your products

WHAT IS IRC


• People are still using IRC– Good: realtime text chat– Bad: not (easily) archived, not (easily) searchable– Learning curve to get involved– Definitely more technical users– Usership is slowly dwindling

STATUS IN 2016


• Old idea, new implementation• Comparable with IRC/ICQ/MSN/etc• Can be open to the public or private

– Archived and searchable• Fills a hole between meetings and email

– Easy/quick interactions for your teams– Great place to build a community around your products

WHAT IS SLACK


• How open source project code is developed• Used by everyone

– Document revisions– Source code– “Infrastructure as Code”

• Predecessors included CVS and Subversion– Single source of truth– Difficult to maintain with a lot of contributors

• Current defacto standard is ‘Git’

REVISION CONTROL SYSTEMS


• Public, free, hosted Git with community features• Quickly became the Git repository for nearly every

major open source project in the world• Github account is now a better résumé than LinkedIn• Allows public-only repositories for free users, private

repositories for paid users• Here’s Mike to tell you more!

INTRODUCTION TO GITHUB


MIKE FILOSAGITHUB

the best way to build and ship software

Mike FilosaGitHub

How software is built

Ops

Design

Security

ProjectMgmt

DomainExperts

CustomerSupport

ExecutiveLeadership

SoftwareDevelopment

Everyone speaks software


Innersource

23

PayPal says InnerSource “raises everybody’s game.”


A common network unlocks participation

24

Visibility and participation across all functions

Discover. Reuse. Contribute.


The GitHub Flow

B U I L D

C O L L A B O R A T E

D E P L O Y


Create a Branch

Open a Pull Request

Merge and deploy

26

The GitHub Flow - Enabling development


Create a Branch

Open a Pull Request

Merge and deploy

27

The GitHub Flow - Experimentation without risk

hypothesis & test

discuss & conclude

accept or discard


Create a Branch

Open a Pull Request

Merge and deployhypothesis & test

discuss & conclude

accept or discard

28

The GitHub Flow - Unlocking team velocity

Transparency replaces status meetings

Asynchronous inform without formal

process


A common network unlocks participation

29

Visibility and participation across all functions

Discover. Reuse. Contribute.


• Open source makes a lot of sense– …But you need a strategy in order to win

• Transparency and collaboration are key• Github and Slack are excellent ways to provide that

transparency and collaboration

CLOSING REMARKS


@EMCcode@mux

emccode.comcommunity.emccode.com

Come visit us at Booth #1044 or in the vLab

Questions?


Data Persistence in the New Container WorldWednesday 3PM

Joshua BernsteinVP of Technology for ETD

Tobi Knaup CEO & Co-Founder of Mesosphere

Guru Session