Default to Open

Default to Open

My keynote at EclipseCon 2018 - https://www.eclipsecon.org/europe2018/keynotes.

75935a034e6c04dfd6f6946a299c3937?s=128

Harish Pillay

October 25, 2018
Tweet

Transcript

  1. 1.

    Insights on Open Source From a 25 Year Old Company

    Harish Pillay Head, Community Architecture and Leadership @harishpillay • hpillay@redhat.com
  2. 2.

    What Happens When You Default to Open Harish Pillay Head,

    Community Architecture and Leadership @harishpillay • hpillay@redhat.com
  3. 4.
  4. 5.

    “Look at your fish” * * apologies to Samuel Scudder

    - http://grammar.about.com/od/classicessays/a/Look-At-Your-Fish-By-Samuel-H-Scudder.htm
  5. 8.

    “No man is fit to be a naturalist, who does

    not know how to take care of specimens.” - Prof Agassiz as remembered by Samuel Scudder
  6. 10.
  7. 11.
  8. 12.

    “Look at your fish” * * apologies to Samuel Scudder

    - http://grammar.about.com/od/classicessays/a/Look-At-Your-Fish-By-Samuel-H-Scudder.htm
  9. 13.

    code “Look at your fish” * * apologies to Samuel

    Scudder - http://grammar.about.com/od/classicessays/a/Look-At-Your-Fish-By-Samuel-H-Scudder.htm
  10. 17.

    17

  11. 18.

    18 Instead of “Why Software FAILS”, this could have read,

    “Why Software Projects Fail” https://spectrum.ieee.org/computing/software/why-software-fails September 2005
  12. 19.

    19 That Sept 2005 IEEE Spectrum article suggests that there

    are 12 common factors why software projects fail
  13. 20.

    20 https://spectrum.ieee.org/computing/software/why-software-fails September 2005 12 most common factors: • 1.

    Unrealistic or unarticulated project goals 2. Inaccurate estimates of needed resources 3. Badly defined system requirements 4. Poor reporting of the project’s status 5. Unmanaged risks 6. Poor communication among customers, developers, and users 7. Use of immature technology 8. Inability to handle the project’s complexity 9. Sloppy development practices 10. Poor project management 11. Stakeholder politics 12. Commercial pressures Why do software projects fail so often?
  14. 22.

    22 https://spectrum.ieee.org/computing/software/why-software-fails September 2005 12 most common factors: • 1.

    Unrealistic or unarticulated project goals 2. Inaccurate estimates of needed resources 3. Badly defined system requirements 4. Poor reporting of the project’s status 5. Unmanaged risks 6. Poor communication among customers, developers, and users 7. Use of immature technology 8. Inability to handle the project’s complexity 9. Sloppy development practices 10. Poor project management 11. Stakeholder politics 12. Commercial pressures Why do software projects fail so often?
  15. 24.

    24 Instead of “Why Software FAILS”, this could have read,

    “Why Projects Fail” https://spectrum.ieee.org/computing/software/why-software-fails September 2005
  16. 25.
  17. 26.
  18. 33.

    33 “Participation in an open source project, whether maintained by

    the Company or by another commercial or non-commercial entity or organization, does not constitute a conflict of interest even where such participant makes a determination in the interest of the project that is adverse to the Company's interests.” * * Page 2, second last paragraph
  19. 34.
  20. 35.
  21. 44.

    44 FOUR FREEDOMS fsf.org Freedom 0: Free to use Anyone

    can use it, however they like. Freedom 1: Free to copy Anyone can get a copy for the cost of media. Freedom 2: Free to modify If I don’t like how it works, I can change it. Freedom 3: Free to distribute I can share my changes.
  22. 45.

    45 GNU PUBLIC LICENSE http://gnu.org Implements the four freedoms. -

    Use, copy, modify, distribute. Built SOLIDLY on copyright. - The author provides additional rights for additional responsibilities.
  23. 46.

    46 LINUX IS BORN From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds) Newsgroups:

    comp.os.minix Subject: What would you like to see most in minix? Message-ID: <1991Aug25.205708.9541@klaava.Helsinki.FI> Date: 25 Aug 91 20:57:08 GMT Organization: University of Helsinki “I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones. This has been brewing since april, and is starting to get ready. I'd like any feedback on things people like/dislike in minix ...” https://tinyurl.com/arfweyo
  24. 48.

    48 “Open Source”1 is a marketing phrase coined2 by Christine

    Peterson3 in 1998 to make “free software” acceptable to newcomers and businesses 1 https://opensource.org/history 2 https://opensource.com/article/18/2/coining-term-open-source-software 3 https://en.wikipedia.org/wiki/Christine_Peterson
  25. 49.

    49 Open Source Initiative – opensource.org - was set up

    in 1998 to be an educational, advocacy, and stewardship organization around collaborative development.
  26. 50.
  27. 51.
  28. 53.

    53 LICENSING IS CRUCIAL Licensing creates the community. - It

    tells us how contributions are handled. Licensing determines the business model. - If you compel source redistribution, how do you build a business? Licensing should be easy. - If it’s too complicated, you lose contributors.
  29. 54.

    54 IT’S ALL ABOUT LICENSING! PERMISSIVE/ WEAK COPYLEFT BSD, MIT,

    Apache, Mozilla, Eclipse, LGPL STRONG COPYLEFT GPL AGPL EUPL Public Domain Non-protective Open Source Licenses Protective Open Source Licenses Proprietary Licenses Trade Secrets All rights relinquished All rights retained Rights in Copyright
  30. 55.

    “Look at your fish” * * apologies to Samuel Scudder

    - http://grammar.about.com/od/classicessays/a/Look-At-Your-Fish-By-Samuel-H-Scudder.htm
  31. 57.
  32. 58.
  33. 61.

    • Idealism to solve a problem • No constraints –

    should it have a product roadmap? • No pain, no gain • Ask forgiveness, not permission • Permissionless innovation • Risk taking – no Product Requirements Document • Fail fast, fail early – learn, grow and evolve Some characteristics of a Project
  34. 63.

    Characteristics of Products • Reduce risk – both yours and

    your customers • Constrained in that it needs to meet the customer requirements • UX/UI finesse • Scalability is important: how would you help the evolution of the product? • Branding: project name <> product name
  35. 65.

    What about People • Project people have a different motivations

    compared with Product people • The motivations of being in a project team is significantly different than being a product team • There may be overlaps, but it is few and far between
  36. 67.
  37. 68.
  38. 71.

    71

  39. 72.

    72

  40. 80.

    15 days ago, on 10/10/18, Microsoft joins the Open Invention

    Network - making more than 60,000 software patents available to all in the Linux & open source ecosystems at no cost and in perpetuity!
  41. 82.

    Comments? Harish Pillay hpillay@redhat.com @harishpillay, 9V1HP Open Unlocks The World’s

    Potential Photo taken 22 Oct 2018 at Red Hat Singapore pantry