Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The Value of Open Source

The Value of Open Source

Robin Johnson

March 03, 2015
Tweet

Other Decks in Programming

Transcript

  1. What is Open Source? •Software that can be freely used

    •Software that can be freely changed •Software that can be freely shared
  2. MIT License Commercial Use Distribution Modification Private Use Sub-licensing Permits:

    Hold Liable Forbids: jQuery, Rails, Api Libs, Me! Used by:
  3. Apache License 2.0 Commercial Use Distribution Modification Private Use Sub-licensing

    Patent Grant Permits: Hold Liable Trademark Use Forbids: Apache, SVN, NuGet Used by:
  4. GPL License (V2 & V3) Commercial Use Distribution Modification Private

    Use Patent Grant Permits: Hold Liable Sub-licensing Forbids: Linux, Git, WordPress Used by:
  5. Why should I contribute? • To make a world of

    better Software • To share knowledge amongst fellow Devs • To help a project reach it’s goals • To sharpen your skills • To join a community!
  6. Why should I Open Source? • Share Knowledge • Gain

    Knowledge • Create community around your project • Potentially save money • Speed up pace of software development
  7. The Big 4 (Why companies are saying yes) • Better

    Code Quality • Agility • Security • Cost
  8. The Value of Code • Code is freely accessible and

    a prominent focus of open source. • Emphasis on Code in Open Source is down to code- sharing tools like GitHub etc. • Code is easily quantified and valued on a per-contributor basis • Code is fickle (in a good way)
  9. The value of Community • A community surrounding a shared

    set of goals • The knowledge being shared amongst that community is invaluable • With more than one pair of eyes, you’re more likely to spot and patch bugs in a timely manner! • The relationships between project owners / community members are very important
  10. Open Source Tools - Project management • Like any project,

    we still need to track issues, and have milestones & roadmaps. • Having an internal Wiki for the project is a good idea too.
  11. The OS Pricing Model • Open Source software doesn’t mean

    no revenue. • The Source Code may be freely available, but that doesn’t mean the software itself has to be. • Dual Licensing allows for a smarter business model • Revenue streams from additional product services: ★ Ongoing professional services ★ Offering the Software as a Service ★ Selling of branded merchandise
  12. Open Source Horror • Sensitive information left in public code

    • Sensitive information trusted to wrong people • Allowing anyone to ‘own’ parts of your software
  13. Open Source Success! • Almost exactly 1 year ago, SendGrid

    open sourced our Docs • 1 year on, we can confirm it was an amazing idea. https://sendgrid.com/docs/index.html Showing last 28 days activity
  14. Get Contributors! • Use Github • Build project modularly •

    Gather metrics on your Contributors and use them • Reward your contributors! • Look after your contributors • TALK TO YOUR CONTRIBUTORS