Slide 1

Slide 1 text

Insights on Open Source From a 25 Year Old Company Harish Pillay Head, Community Architecture and Leadership @harishpillay • [email protected]

Slide 2

Slide 2 text

What Happens When You Default to Open Harish Pillay Head, Community Architecture and Leadership @harishpillay • [email protected]

Slide 3

Slide 3 text

A 6 act talk

Slide 4

Slide 4 text

Slide 5

Slide 5 text

“Look at your fish” * * apologies to Samuel Scudder - http://grammar.about.com/od/classicessays/a/Look-At-Your-Fish-By-Samuel-H-Scudder.htm

Slide 6

Slide 6 text

Haemulon CC BY Brian Gratwicke https://en.wikipedia.org/wiki/Haemulon#/media/File:Haemulon_flavolineatum_French_grunt.jpg

Slide 7

Slide 7 text

Samuel Hubbard Scudder https://commons.wikimedia.org/wiki/ File:Samuel_Hubbard_Scudder_1837-1911.jpg#/ media/File:Samuel_Hubbard_Scudder_1837-1911.jpg Professor Louis Agassiz https://en.wikipedia.org/wiki/Louis_Agassiz

Slide 8

Slide 8 text

“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

Slide 9

Slide 9 text

Haemulon CC BY Brian Gratwicke https://en.wikipedia.org/wiki/Haemulon#/media/File:Haemulon_flavolineatum_French_grunt.jpg

Slide 10

Slide 10 text

Slide 11

Slide 11 text

Slide 12

Slide 12 text

“Look at your fish” * * apologies to Samuel Scudder - http://grammar.about.com/od/classicessays/a/Look-At-Your-Fish-By-Samuel-H-Scudder.htm

Slide 13

Slide 13 text

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

Slide 14

Slide 14 text

14 Why Code?

Slide 15

Slide 15 text

15 Why Open?

Slide 16

Slide 16 text

16 Really, why?

Slide 17

Slide 17 text

17

Slide 18

Slide 18 text

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

Slide 19

Slide 19 text

19 That Sept 2005 IEEE Spectrum article suggests that there are 12 common factors why software projects fail

Slide 20

Slide 20 text

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?

Slide 21

Slide 21 text

21 Are those failures because of code?

Slide 22

Slide 22 text

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?

Slide 23

Slide 23 text

23 Or is it because of failure to collaborate?

Slide 24

Slide 24 text

24 Instead of “Why Software FAILS”, this could have read, “Why Projects Fail” https://spectrum.ieee.org/computing/software/why-software-fails September 2005

Slide 25

Slide 25 text

Slide 26

Slide 26 text

Slide 27

Slide 27 text

27 “My code repo is mine, and your repo is yours!”

Slide 28

Slide 28 text

28 THE OPEN SOURCE WAY

Slide 29

Slide 29 text

29 Create. Share. Collaborate. Rinse and Repeat! THE OPEN SOURCE WAY

Slide 30

Slide 30 text

30 Permissionless Innovation

Slide 31

Slide 31 text

31 Ask for forgiveness, not permission

Slide 32

Slide 32 text

32 https://investors.redhat.com/corporate-governance/governance-documents

Slide 33

Slide 33 text

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

Slide 34

Slide 34 text

Slide 35

Slide 35 text

Slide 36

Slide 36 text

36 How the Open Source Development Model Succeeded

Slide 37

Slide 37 text

VERY BRIEF HISTORY OF FREE SOFTWARE

Slide 38

Slide 38 text

38 IOW, how did we get here?

Slide 39

Slide 39 text

39 1980-1984

Slide 40

Slide 40 text

40 Richard M Stallman (photo from 2014)

Slide 41

Slide 41 text

41 Xerox 9700 Laser Printer https://en.wikipedia.org/wiki/Xerox_9700 http://www.oreilly.com/openbook/freedom/ch01.html “Free as in freedom” Richard Stallman’s Crusade for Free Software

Slide 42

Slide 42 text

42 GNU’s Not Unix

Slide 43

Slide 43 text

43 Established 4th October, 1985

Slide 44

Slide 44 text

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.

Slide 45

Slide 45 text

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.

Slide 46

Slide 46 text

46 LINUX IS BORN From: [email protected] (Linus Benedict Torvalds) Newsgroups: comp.os.minix Subject: What would you like to see most in minix? Message-ID: <[email protected]> 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

Slide 47

Slide 47 text

47 http://catb.org/~esr/writings/homesteading/cathedral-bazaar/

Slide 48

Slide 48 text

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

Slide 49

Slide 49 text

49 Open Source Initiative – opensource.org - was set up in 1998 to be an educational, advocacy, and stewardship organization around collaborative development.

Slide 50

Slide 50 text

Slide 51

Slide 51 text

Slide 52

Slide 52 text

52 LICENSING

Slide 53

Slide 53 text

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.

Slide 54

Slide 54 text

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

Slide 55

Slide 55 text

“Look at your fish” * * apologies to Samuel Scudder - http://grammar.about.com/od/classicessays/a/Look-At-Your-Fish-By-Samuel-H-Scudder.htm

Slide 56

Slide 56 text

Haemulon CC BY Brian Gratwicke https://en.wikipedia.org/wiki/Haemulon#/media/File:Haemulon_flavolineatum_French_grunt.jpg

Slide 57

Slide 57 text

Slide 58

Slide 58 text

Slide 59

Slide 59 text

The Incredibly Fine Balance between Open Source Projects and Open Source Products

Slide 60

Slide 60 text

What is an Open Source Project?

Slide 61

Slide 61 text

● 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

Slide 62

Slide 62 text

What is an Open Source Product?

Slide 63

Slide 63 text

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

Slide 64

Slide 64 text

Projects and Products Need People

Slide 65

Slide 65 text

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

Slide 66

Slide 66 text

Source Code License Community Free and Open Source Software

Slide 67

Slide 67 text

No content

Slide 68

Slide 68 text

Slide 69

Slide 69 text

Slide 70

Slide 70 text

70 Red Hat Linux 1996

Slide 71

Slide 71 text

71

Slide 72

Slide 72 text

72

Slide 73

Slide 73 text

73 Page 7 – Red Hat Linux User’s Guide 1996

Slide 74

Slide 74 text

Fast forward a few years ...

Slide 75

Slide 75 text

75 COMMUNISTS Microsoft CEO Steve Ballmer, July 2000 http://www.theregister.co.uk/2000/07/31/ms_ballmer_linux_is_communism/ Image: https://www.flickr.com/photos/daviderickson/718933691 CC BY-SA 2.0

Slide 76

Slide 76 text

76 https://www.redhat.com/en/about/patent-promise

Slide 77

Slide 77 text

77 http://www.theregister.co.uk/2004/11/18/ballmer_linux_lawsuits/

Slide 78

Slide 78 text

11 years later ...

Slide 79

Slide 79 text

79 Microsoft CEO Satya Nadella January 2015 https://youtu.be/54hHr8ye2kE

Slide 80

Slide 80 text

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!

Slide 81

Slide 81 text

Slide 82

Slide 82 text

Comments? Harish Pillay [email protected] @harishpillay, 9V1HP Open Unlocks The World’s Potential Photo taken 22 Oct 2018 at Red Hat Singapore pantry