Leverage Open Source with GitHub

Leverage Open Source with GitHub

Various aspects of the opensource eco-system. Talk prepared for LION @ TheFamily

71012cb8bfc5382943c202690e3562a8?s=128

Alain Hélaïli

November 18, 2016
Tweet

Transcript

  1. 1.

    the best way to build and ship software Leverage Open

    Source with GitHub a @helaili - @AlainHelaili - ! helaili@github.com
  2. 2.
  3. 3.

    the best way to build and ship software Git 3

    " • Started by Linus Torvalds 2005 (search “torvalds git” on youtube) • Easy branching and merging - content oriented, remembers origin • Small and fast - local operations, smaller repos • Distributed - VCS on my laptop, full copy incl. history • Data assurance - sha1, gpg • Staging area - crafted, meaningful commits • Free and open source
  4. 4.

    the best way to build and ship software GitHub key

    facts 4 " FOUNDED 2008 EMPLOYEES 600 UNIVERSITIES USING GITHUB 1,000+ TOTAL 
 REGISTERED USERS 15M TOTAL REPOSITORIES 40M PAYING ORGANIZATIONS >75,000
  5. 6.

    "

  6. 9.

    "

  7. 10.

    "

  8. 11.

    "

  9. 13.

    the best way to build and ship software All businesses

    will evolve into software businesses 13 "
  10. 15.

    the best way to build and ship software Why open

    sourcing code 15 " • Great advertising for you and your company… translat[ing] into goodwill for [your company] and more superfans than ever before • Attract outside contributions : create a force multiplier that helps you get more work done faster and cheaper. More users means more use cases being explored which means more robust code • Attract talent : Smart people like to hang out with other smart people. Smart developers like to hang out with smart code. • Best technical interview possible, the one you don’t have to do because the candidate is already kicking • Retain talents
  11. 17.

    How people build software " a framework for assessing the

    effectiveness of behaviors, practices and processes, and identifying what capabilities to acquire next in order to produce the desired outcomes M A T U R I T Y M O D E L F O R A D O P T I N G O P E N S O U R C E
  12. 18.

    How people build software " MATURE UNDEVELOPED Evaluate Improve +

    " M A T U R I T Y M O D E L F O R A D O P T I N G O P E N S O U R C E
  13. 19.

    the best way to build and ship software 19 "

    a lot of work that wasn't truly open source — i.e. out-of-the-box useful to the community at-large The enthusiasm our team showed for open source led the Guild to next develop a set of Open Source First principles to institutionalize this openness. These principles encourage our engineers to share their code instead of hide it inside private repos, as well as "take ownership," "be safe," "provide documentation," and "ask for help."
  14. 20.

    How people build software " Maturity Model for Adopting Open

    Source CONSUMING CONTRIBUTING RELEASING EMBRACING Using open source software. Contributing back to the projects you use. Creating new open source projects. Strategically participating in open source.
  15. 21.

    How people build software " Maturity Model for Adopting Open

    Source CONSUMING CONTRIBUTING RELEASING EMBRACING Using open source software. What are the basics of open source? How do I find projects? How do I evaluate the quality and health of projects? How do I stay on top of security vulnerabilities? What are the basics of licensing? What do I need to do to comply with the license?
  16. 22.

    How people build software " Maturity Model for Adopting Open

    Source CONSUMING CONTRIBUTING RELEASING EMBRACING Contributing back to the projects you use. How do I report issues? How do I use GitHub? What do I need to know about IP?
  17. 23.

    How people build software " Maturity Model for Adopting Open

    Source CONSUMING CONTRIBUTING RELEASING EMBRACING Creating new open source projects. How do I get my source code ready for release? How do I choose a license? What else do I need to know about IP? How do I build a community? What other tools do I need for my community?
  18. 24.

    "

  19. 25.

    How people build software " Maturity Model for Adopting Open

    Source CONSUMING CONTRIBUTING RELEASING EMBRACING Strategically participating in open source. How can we get a competitive advantage? What open source releases show leadership? How effective is our open source involvement? What communities do we want to hire from? How do we work like an open source project internally?
  20. 27.

    "

  21. 28.

    the best way to build and ship software How will

    software be built in the future? 28 " InnerSource: The power of open source within the walls of the enterprise.
  22. 29.

    the best way to build and ship software Why do

    PayPal, Scania and IBM use InnerSource? 29 "
  23. 30.

    the best way to build and ship software What are

    the core tenets of InnerSource? 30 " • Everyone is expected to contribute and participate in reviews and mentoring • Contributions are judged based on their merits • All decisions are discussed publicly, stored indefinitely, and can be searched • Code and commentary are widely available • Autonomous organization of teams, self organizing and alignment
  24. 33.

    the best way to build and ship software Choose your

    license 33 " • License = business model • Fremium • Embed • Certification • Liability • Support • Ecosystem
  25. 44.
  26. 47.

    # $ % & ' ' ( ) % *

    + ' ' Upstream Origin Fork
  27. 48.

    # $ % & ' ' ( ) % *

    + ' ' Upstream Origin Create a Feature Branch
  28. 49.

    # $ % & ' ' ( ) % *

    + ' ' Upstream Origin Add commits
  29. 50.

    # $ % & ' ' ( ) % *

    + ' ' Upstream Origin Open a Pull Request
  30. 51.
  31. 52.

    # $ % & ' ' ( ) % *

    + ' ' Upstream Origin Discuss and Review Code
  32. 55.

    # $ % & ' ' ) % * +

    ' ' Upstream Origin Merge (
  33. 56.

    # $ % & ' ' ( ) % *

    + ' ' Upstream Origin Pull from Upstream Master
  34. 58.

    # * $ + $ + + * * $

    $ $ $ $ Dictator Lieutenants Public contributors
  35. 59.

    # * $ + $ + + * * $

    $ $ $ $ Dictator Lieutenants Public contributors & & & & & & (
  36. 60.

    # * $ + $ + + * * $

    $ $ $ $ Dictator Lieutenants Public contributors
  37. 63.

    the best way to build and ship software Gerrit 63

    " • Body Level One • Body Level Two • Body Level Three • Body Level Four • Body Level Five