1 / 13

The evolution of open source

Ragavan Srinivasan opensource.hp.com Hewlett Packard Company Oct 5, 2006. The evolution of open source. Open Source . & Linux . Agenda 1. A Brief History of Open source software Why do people use/contribute to OSS?. What comes to mind when you say FLOSS?. Depends on who you ask

donoma
Download Presentation

The evolution of open source

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Ragavan Srinivasan opensource.hp.com Hewlett Packard Company Oct 5, 2006 The evolution of open source

  2. Open Source & Linux Agenda 1 • A Brief History of Open source software • Why do people use/contribute to OSS?

  3. What comes to mind when you say FLOSS? Depends on who you ask Dental hygiene :-) Freedom Free beer Linux Licenses GPL Microsoft

  4. “FLOSS” is three things Methodology Community Licenses • Almost 60 licenses today • Some require that code changes be returned to the community at large • These are called copyleft or reciprocal • They are not viral • This requirement is what makes the methodology work • Other licenses are similar to the public domain and have few requirements • Copyrights are still a core foundational element of all open source licenses • Any collection of developers with a common interest • Historically made up of free agents • Increasingly funded by large companies sharing development costs • Governments and academia also contributing at an increasing pace • Communal, shared development • Various projects each with their own subculture • Governance models vary widely, some autocratic, others consensus based • Very few roadmaps, but some projects are starting to publish them • Influence and control is achieved by being integrated & involved • Individuals are largely in control, not companies January 18, 2006

  5. Open Source & Linux spanning the enterprise over time Client Devices Internet access Line of business Enterprise data Servers + Storage + Manageability + Services and Support Mature Growing Emerging Penetration over time Business applications Data/content Server/warehouse Networkedge Infrastructure • ERP • SCM • CRM • HR • Proxy • Caching • VPN • Firewall • Gateways • WAP • VoIP • Directory • Security • Load balance • File/print • Web • E-mail • NAS • Databases • Serverconsolidation Compute clusters Financial, R&D, biotech, energy, DCC, visualization

  6. Why do people use and contribute to OSS?

  7. Some common reasons Individuals to scratch an itch philosophical reasons true altruism competitive nature of humans (http://www.wikimatrix.org/) Companies all of the above cost (savings, spreading) vendor/platform independence (HP + OpenLDAP) don't reinvent the wheel (e.g. xml parsers)

  8. FLOSS usage models As 'lego's/building blocks Unix pipe Decentralized nature of the internet's infrastructure HP's IMAP Proxy example Focus shifting towards gluing pieces together To provide varied levels of service Read-only, high-volume, low value transactions

  9. Some common challenges Open source governance licenses maturity too many options supportability Open Source Licenses Non-reciprocal Reciprocal Patent clauses NoRestrictions Restrictions GPL LGPL MPL IBM Original BSD Apache W3C MIT January 18, 2006

  10. Why Companies Need to Manage Open Source Use of open source is pervasive and not always visible how and where used, who contributes to community, etc. Open source licenses need to be understood and managed HP tracks 180 unique licenses today Open source has compelling value proposition – lower TCO, more choice, vendor neutral, engineering productivity boost

  11. HP Learnings in Open Source Management Define and communicate open source policies and guidelines Develop open source training and awareness Inventory and track all open source projects – use, code re-use, community contributions, shipments of products w/ open source, etc. Establish open source governance process Establish internal open source community

  12. FLOSS + Education Helps students “learn how to learn” Free content helps global reach of knowledge (e.g. MIT's open courseware) Powers revolutionary new technologies (OLPC) Fosters collaborative creation and dissemination of knowledge (Wikipedia) Solid way to build credibility (e.g. Google's SoC participants)

  13. www.hp.com/go/linux

More Related