EMC World 2016 - code.10 Jumpstart your Open Source Presence through new Collaboration Tools
•Download as PPTX, PDF•
1 like•461 views
Building a great open source strategy starts from the inside. A strategy that focuses on real-time communication, open and collaborative discussions tends to be more successful with their open source initiatives and hiring the right talent. Learn about the tools such as GitHub and Slack that can help align your company to open source.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (16)
Similar to EMC World 2016 - code.10 Jumpstart your Open Source Presence through new Collaboration Tools
Similar to EMC World 2016 - code.10 Jumpstart your Open Source Presence through new Collaboration Tools (20)
Recently uploaded
Recently uploaded (20)
EMC World 2016 - code.10 Jumpstart your Open Source Presence through new Collaboration Tools
- 1. 1© Copyright 2016 EMC Corporation. All rights reserved. 1© Copyright 2016 EMC Corporation. All rights reserved. JUMPSTART YOUR OPEN SOURCE PRESENCE WITH NEW COLLAB TOOLS DREW SMITH, EMC {code} MIKE FILOSA, GITHUB
- 2. 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?
- 3. 4© Copyright 2016 EMC Corporation. All rights reserved. • 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?
- 4. 5© Copyright 2016 EMC Corporation. All rights reserved. 5© Copyright 2016 EMC Corporation. All rights reserved. WHAT IS AN OPEN SOURCE STRATEGY AND WHY SHOULD YOU CARE
- 5. 6© Copyright 2016 EMC Corporation. All rights reserved. THE GAME IS CHANGING
- 6. 7© Copyright 2016 EMC Corporation. All rights reserved. • 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:
- 7. 8© Copyright 2016 EMC Corporation. All rights reserved. • Cost savings on software licensing • Increased technical/software velocity • Better employee recruitment and retention • Harness creativity and collaboration YOU SHOULD CARE BECAUSE:
- 8. 9© Copyright 2016 EMC Corporation. All rights reserved. WHO IS USING OPEN SOURCE?
- 9. 10© Copyright 2016 EMC Corporation. All rights reserved. • Software development teams • Server/Internet operations teams • Internal IT • Sales/Marketing WHAT THIS CAN LOOK LIKE
- 10. 11© Copyright 2016 EMC Corporation. All rights reserved. • 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
- 11. 12© Copyright 2016 EMC Corporation. All rights reserved. • 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
- 12. 13© Copyright 2016 EMC Corporation. All rights reserved. • 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
- 13. 14© Copyright 2016 EMC Corporation. All rights reserved. • Larger communities gather for in-person Meetups – Though this • Also often use IRC for real time interaction OPEN SOURCE COMMUNITIES
- 14. 15© Copyright 2016 EMC Corporation. All rights reserved. • 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
- 15. 16© Copyright 2016 EMC Corporation. All rights reserved. • 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
- 16. 17© Copyright 2016 EMC Corporation. All rights reserved. • 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
- 17. 18© Copyright 2016 EMC Corporation. All rights reserved. • 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
- 18. 19© Copyright 2016 EMC Corporation. All rights reserved. • 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
- 19. 20© Copyright 2016 EMC Corporation. All rights reserved. 20© Copyright 2016 EMC Corporation. All rights reserved. MIKE FILOSA GITHUB
- 20. the best way to build and ship software Mike Filosa GitHub
- 21. How software is built Ops Design Security Project Mgmt Domain Experts Customer Support Executive Leadership Software Development Everyone speaks software
- 22. the best way to build and ship software Innersource 23 PayPal says InnerSource “raises everybody’s game.”
- 23. the best way to build and ship software A common network unlocks participation 24 Visibility and participation across all functions Discover. Reuse. Contribute.
- 24. the best way to build and ship software 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
- 25. How software is built Create a Branch Open a Pull Request Merge and deploy 26 The GitHub Flow - Enabling development
- 26. How software is built Create a Branch Open a Pull Request Merge and deploy 27 The GitHub Flow - Experimentation without risk hypothesis & test discuss & conclude accept or discard
- 27. How software is built Create a Branch Open a Pull Request Merge and deploy hypothesis & test discuss & conclude accept or discard 28 The GitHub Flow - Unlocking team velocity Transparency replaces status meetings Asynchronous inform without formal process
- 28. the best way to build and ship software A common network unlocks participation 29 Visibility and participation across all functions Discover. Reuse. Contribute.
- 29. 30© Copyright 2016 EMC Corporation. All rights reserved. • 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
- 30. 31© Copyright 2016 EMC Corporation. All rights reserved. @EMCcode @mux emccode.com community.emccode.com Come visit us at Booth #1044 or in the vLab Questions?
- 31. 32© Copyright 2016 EMC Corporation. All rights reserved. Data Persistence in the New Container World Wednesday 3PM Joshua Bernstein VP of Technology for ETD Tobi Knaup CEO & Co-Founder of Mesosphere Guru Session
- 32. 33© Copyright 2016 EMC Corporation. All rights reserved. 33© Copyright 2016 EMC Corporation. All rights reserved.
- 33. 34© Copyright 2016 EMC Corporation. All rights reserved.
Editor's Notes
- Fact: open source is here to stay The business model is fundamentally different Whether you’re releasing your projects open source or just embracing the tools
- Who is using open source?
- Basically everybody! But is it just internet services? No.
- The first element of our approach: unite all developers on a single network. Today that network numbers some 10 million people and that network makes them all more productive — across every language (java, .net, etc) and every application type. Discover, Reuse, Contribute. Discover and share existing code components. The code that put the rover on mars and the code that my nephew created for his robotics competition and everything in between are on GitHub. The ability to discover and reuse components turns development into something closer to lego as opposed to net-new creation every time. This ultimately means GitHub users can build software faster than anyone else. Inside the enterprise, eliminate organizational silos: a common network enables all code to be discoverable, applying the same concept internally. Your developers are already here More than half the world’s developers use GitHub today, so even if you are not using GitHub in your organization, its almost certain that your developers go home and use GitHub at night. Benefits: easier recruiting, faster on-boarding. Visibility Uniting non-developers on that same network means that an organization can build software the way that software companies build software: with participation from across the org. For business users, its like collaborating on the architectural drawings while the house is being built
- The SECOND aspect of our approach: enable GitHub as a platform that supports the broader application lifecycle. For the vast majority of users. this is how they use GitHub today. Literally every aspect of the development lifecycle integrates into GitHub regardless of type. Everything is a check in / checkout from GitHub as the application moves through the process.
- The second aspect of our approach: PROVIDE THE WORLDS BEST DEVELOPMENT WORKFLOW, the GitHub Flow. This was introduced in 2008 and refined through the experience of the open source community as a means to enable groups of people to build software together. The basic approach: - there is a core trunk of the project - anyone can create a “branch” — essentially a copy — and make changes to it - this can be reintroduced to the main trunk through a ‘pull request’ at the discretion of the project lead. It is this simple workflow that underpins the way that people build software today.
- [BENEFIT] While in practice pretty simple, what this enables is pretty profound: it facilitates a culture of ‘experimentation without risk’ which is really the promise of agile development — and a hallmark of the startup approach. When I create a branch, I take a copy of the project (or component) and test a hypothesis for a better or different way of building that element. I can then come to a conclusion (does this work or not), and submit it back via a pull request than can either be accepted or discarded. Because I am always working with a local copy, there is little risk: I can experiment, test, conclude and discard if my approach was invalid. This is how developers and teams of developers build great software.
- [BENEFIT] This also has a secondary benefit that teams quickly see: streamlined communication. Because there is a written record of all changes, teams work asynchronously, meaning developers can focus on their flow of productivity. It also means a remarkable level of transparency: ideas win on merit alone (a hallmark of open source) rather than project management. This is how the open source community has been able to develop software, and today can be applied to any project. The whole principle of Developer Flow is a really big one for us.
- The first element of our approach: unite all developers on a single network. Today that network numbers some 10 million people and that network makes them all more productive — across every language (java, .net, etc) and every application type. Discover, Reuse, Contribute. Discover and share existing code components. The code that put the rover on mars and the code that my nephew created for his robotics competition and everything in between are on GitHub. The ability to discover and reuse components turns development into something closer to lego as opposed to net-new creation every time. This ultimately means GitHub users can build software faster than anyone else. Inside the enterprise, eliminate organizational silos: a common network enables all code to be discoverable, applying the same concept internally. Your developers are already here More than half the world’s developers use GitHub today, so even if you are not using GitHub in your organization, its almost certain that your developers go home and use GitHub at night. Benefits: easier recruiting, faster on-boarding. Visibility Uniting non-developers on that same network means that an organization can build software the way that software companies build software: with participation from across the org. For business users, its like collaborating on the architectural drawings while the house is being built