1. © 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice Open Source How and Why? Bdale Garbee Open Source & Linux Chief Technologist

2. 2 Open Source: How and Why? Who is Bdale? First contribution to Free Software circa 1979 HP Open Source & Linux Chief Technologist Contributor to Debian GNU/Linux since October1994, including service as Debian Project Leader, early design of infrastructure, porting to several new architectures, maintaining many packages. Currently serve as chairman of the Debian Technical Committee. 2008 FNILL Lutece d'Or as “FLOSS Personality of the Year” President, Software in the Public Interest Board member of Linux Foundation Board member of The Document Foundation Board member of FreedomBox Foundation

3. 3 Open Source: How and Why? Who is Bdale? Long history of hobby involvement in amateur radio – Founding member of “tcp-group”, developed KA9Q stack – Life member of AMSAT Original “Microsat” program spawned an entire industry Worked on AO-40 “RUDAK” communications processor Project lead for GPS receiver on AO-40 – Occasional contributor to GNU Radio Packaging for Debian and derivative distributions High-profile presentations about SDR at Linux conferences High power model rocket enthusiast...

5. 5 Open Source: How and Why?

6. 6 What I'll try to cover today FOSS essential concepts Thoughts about FOSS licenses and business models Enabling Open Innovation

7. © Copyright 2010 Hewlett-Packard Development Company, L.P. 7 7 FOSS Essential Concepts

8. 8 Open Source: How and Why? It is everywhere Examples of Free & Open Source Software

9. 9 Open Source: How and Why? FSF's Four Freedoms Freedom to run the program, for any purpose. Freedom to study how the program works, and change it to make it do what you wish. Access to the source code is a precondition for this. Freedom to redistribute copies so you can help your neighbor. Freedom to improve the program, and release your improvements (and modified versions in general) so that the whole community benefits. Access to the source code is a precondition for this.

10. 10 Open Source: How and Why? Free Software or Open Source? Note that source code access is a precondition, not a motivator in and of itself In business, we tend to use these terms as if they were synonyms.. or use tokens like “FOSS” to cover both The term “Open Source” was coined to avoid having to explain “Free as in freedom, not as in beer”, but this is a uniquely-English problem. Romance languages have different words. Freedom is an economic motivator!

11. 11 Open Source: How and Why? Community Development Model A key attribute of Linux and many Open Source applications is that they are developed and supported “by the community” What does that mean? −No one company in charge −A range of contributors with varied interests, abilities, and motivations

12. 12 Open Source: How and Why? Freedom of Choice Users have flexibility in how they acquire support for open source technology Any user can become a developer, or pay someone to develop or support open source software on their behalf If “upstream” ever behaves unacceptably, developers have the power to “fork”

13. 13 Open Source: How and Why? FOSS Projects Most projects begin with an individual or very small group coding a prototype to “scratch an itch” Once a threshold of utility is reached, others start using the software, debug and enhancement follows Successful projects have a vibrant community of contribution around a central maintainer Aggregation and integration build user base License choice and governance model define the shape of the community that emerges around a project

14. © Copyright 2010 Hewlett-Packard Development Company, L.P. 14© Copyright 2010 Hewlett-Packard Development Company, L.P. 14 Licenses & Business Models

15. 15 Open Source: How and Why? Copyright Holders FOSS licensing has its basis in copyright law The initial author / copyright holder of a piece of code gets to choose the license(s) Without an explicit license assertion, no rights are conveyed... thanks to “copyright by default” License choice can have a profound impact on the nature and behavior of the community formed Choosing to “join a project” means accepting the terms of any licenses already in place

16. 16 Open Source: How and Why? What do these companies have in common? All have been sued for violations of Open Source license terms Undisclosed financial settlements, appointment of Open Source compliance officers, publish source code on web sites, notify customers Difficulty working with the Open Source Community Publicly embarrassed Not a list your company wants to be on!

17. 17 Open Source: How and Why? Open Source Software licenses More than 60 licenses today as recognized by OSI Two basic types of licenses  Reciprocal licenses that require code changes to be returned to the community at large. This type of license is also called a Copyleft license.  Licenses that permit modified versions to be retained as proprietary and permit arbitrary integration into proprietary software.

18. 18 Open Source: How and Why? Two types of FOSS licenses GNU LGPL MIT IBM Mozilla W3C Apache No impact on other code Copyleft GNU GPL FOSS “as-is” BSD Eclips e

19. 19 Open Source: How and Why? Derivative Works (GPL) HP Proprietary Program GPL Libraries, classes, or code NO! Proprietary Program GPL Wrapper GPL Libraries, classes, or code Probably NOT! https://pts.usa.hp.com/drupal/node/254 Proprietary Program Fork/Exec API or Command Line Generally OK. But, there are exceptions! GPL Program

20. 20 Open Source: How and Why? Derivative Works (other licenses) Proprietary Code MIT, BSD, Apache code Permissive Licenses Copyright notices & license must be maintained in addition to other requirements Proprietary Code (e.g. hpvalue.c) Weak Copyleft Licenses MPL/EPL code (e.g. mpl.c) Generally, proprietary code must be maintained in a separate file Proprietary Program LGPL LGPL, GPL + Exception Libraries Dynamic linking/run-time loading preferred for LGPL Changes here must be licensed under LGPL

21. 21 Open Source: How and Why? GPLv3: Issues Three provisions in the GPLv3 motivate taking particular care when interacting with software using this license Explicit patent license Embedded software Agreements granting licenses to patents

22. 22 Open Source: How and Why? Business models Remember, “Open Source” is not a business model! Can enable the sale of hardware Sell services, such as training and support Give source away, charge for binary access Open a core, keep other parts of an ecosystem (add-ons, management tools, etc) proprietary Latest version to subscribers, older versions open Turn someone else's profit pool into a commodity Harness the creativity of a very diverse community

23. © Copyright 2010 Hewlett-Packard Development Company, L.P. 23© Copyright 2010 Hewlett-Packard Development Company, L.P. 23 Open Innovation

24. 24 Open Source: How and Why? Innovation Where does innovation really happen? Surprisingly often, it comes because “amateurs” do something “industry” or “the establishment” doesn't believe they can do...

25. 25 Open Source: How and Why? Recognize these guys?

26. 26 Open Source: How and Why? Does this help?

27. 27 Open Source: How and Why? How about this guy?

28. 28 Open Source: How and Why?

29. 29 Open Source: How and Why? What's my point? One significant consequence of lowering the barriers to entry combined with the community development process around open source, is that people we don't even know exist are empowered to invent things we can't imagine... Collaboration is fun! Companies and individuals can take advantage of the innovations that result!

30. 30 Open Source: How and Why? Why Enable Open Innovation? Focus investments on things that truly differentiate! Taking advantage of existing open source technology can help reduce our spend on non- differentiating elements of products. Maximizing community involvement grows the body of technology that we do not need to invest in to take advantage of in the future. Building community enthusiasm around products is cheap, but not free −Must get the basics right.. license compliance −Choosing to intentionally build community

31. 31 Open Source: How and Why? Being Open What it does not mean: – Giving everything we do away for free – Getting everything we want for free

32. 32 Open Source: How and Why? Perceptions To benefit from Open Innovation around our products, we need community enthusiasm Open source community enthusiasm is driven largely by contribution and collaboration Adding a single motivated developer to an open source project can make a huge difference Assigning an engineer to develop functionality in an open source community yields real benefits, and builds valuable community perception equity

33. 33 Open Source: How and Why? Building Open Source Equity Outsourcing to partners is a reasonable way to run experiments without the risk of commitment, but brings no technical or reputation equity When badged employees work on open source projects, expertise gained can be re-applied Contributors have the ability to directly influence future project technical directions

34. © Copyright 2010 Hewlett-Packard Development Company, L.P. 34 HP open source community participation Areas of leadership, contribution, and sponsorship Platform Enablement Open Source Policy and GovernancePrinting and Imaging Tesseract OCR & – testing, performance, management, virtualization, and security SIM OpenView VMM Open Source Policy & Compliance Services

35. 35 Open Source: How and Why? The Bottom Line: Individuals Matter In the open source world, it's all about the code Getting code accepted involves a combination of technical prowess and reputation The reputation that matters is individual – Linus famously observed that he didn't even know the corporate affiliation of most kernel developers Open source engagement can be a career development element for many of us!

36. 36 Open Source: How and Why? Never doubt that a small group of thoughtful, committed citizens can change the world. Indeed, it is the only thing that ever has. Margaret Mead