Playing By The Rules Getting Corporate Blessing to Use Open Source Software Phil Robb R&D Section Manager Open Source & Linux Organization HP
The Evolution of Our Computing Environment….
Development Building Blocks September 2006 OSLO staff review // HP confidential
The Affects of FOSS on Traditional Software Markets Established Markets have been pillaged Compilers Toolchains & Development Environments  Enterprise Operating Systems Embedded Operating Systems Web Servers Established Strongholds have been weakened Oracle, Weblogic, IBM all now offer “Free” or “Community” versions. New Markets Never Began Web Service protocols / Java Tools MS compatible File and Print Services Very difficult for a commercial co to invest what’s needed to engineer a samba competitor then try to charge for it’s use Blogging & Wiki Software
HP’s Interaction with Open Source Software Internal Usage OpenLDAP, Jabber, Email, etc… Incorporated in our Software Products OpenView, Insight Manager, … many Software Products Ship Open Source Distributions Red Hat, Suse, etc… Embedded in our Hardware Products Printers, Televisions, Storage Devices, etc… Active Participants in The Community Contributors in Dozens of Projects Maintainers in Several Projects
HP Learnings & open source management Defined and communicated corporate-wide policies  Gain Open Source Legal expertise  Corporate-wide Training and Awareness  Inventory and tracking of all opensource projects Use, code re-use, opensource contributions, shipments of products w/opensource, etc. Open Source Governance -HP OSRB (Open Source Review Board)  Acquire or build tools to ease process adoption and compliance
Customer Experiences and Learnings Tomcat Struts Spring
Customer’s need for a “Librarian” Where does the software come from? Is it mature? What are the License Obligations? How is it supported Is it secure? Is it stable/reliable? What version should I be running? Is it LSB compliant?
Librarian’s need for tools
IT Software Governance Project Goals Budget Resources Schedule Health Commercial SW Used FOSS Used Vulnerabilities Roadmap What Software Where Used License Obligation Usage Restrictions/Policy IP Contamination Origin Maturity Inter-compatibility Support Health Vulnerabilities Roadmap What Software Where Used Cost License Obligations Entitlements Renewals Vulnerabilities Roadmap Health Internally Developed  Software Free & Open  Source  Software Commercial  Software
Thank you for your attention Questions?

Os Robb

  • 1.
    Playing By TheRules Getting Corporate Blessing to Use Open Source Software Phil Robb R&D Section Manager Open Source & Linux Organization HP
  • 2.
    The Evolution ofOur Computing Environment….
  • 3.
    Development Building BlocksSeptember 2006 OSLO staff review // HP confidential
  • 4.
    The Affects ofFOSS on Traditional Software Markets Established Markets have been pillaged Compilers Toolchains & Development Environments Enterprise Operating Systems Embedded Operating Systems Web Servers Established Strongholds have been weakened Oracle, Weblogic, IBM all now offer “Free” or “Community” versions. New Markets Never Began Web Service protocols / Java Tools MS compatible File and Print Services Very difficult for a commercial co to invest what’s needed to engineer a samba competitor then try to charge for it’s use Blogging & Wiki Software
  • 5.
    HP’s Interaction withOpen Source Software Internal Usage OpenLDAP, Jabber, Email, etc… Incorporated in our Software Products OpenView, Insight Manager, … many Software Products Ship Open Source Distributions Red Hat, Suse, etc… Embedded in our Hardware Products Printers, Televisions, Storage Devices, etc… Active Participants in The Community Contributors in Dozens of Projects Maintainers in Several Projects
  • 6.
    HP Learnings &open source management Defined and communicated corporate-wide policies Gain Open Source Legal expertise Corporate-wide Training and Awareness Inventory and tracking of all opensource projects Use, code re-use, opensource contributions, shipments of products w/opensource, etc. Open Source Governance -HP OSRB (Open Source Review Board) Acquire or build tools to ease process adoption and compliance
  • 7.
    Customer Experiences andLearnings Tomcat Struts Spring
  • 8.
    Customer’s need fora “Librarian” Where does the software come from? Is it mature? What are the License Obligations? How is it supported Is it secure? Is it stable/reliable? What version should I be running? Is it LSB compliant?
  • 9.
  • 10.
    IT Software GovernanceProject Goals Budget Resources Schedule Health Commercial SW Used FOSS Used Vulnerabilities Roadmap What Software Where Used License Obligation Usage Restrictions/Policy IP Contamination Origin Maturity Inter-compatibility Support Health Vulnerabilities Roadmap What Software Where Used Cost License Obligations Entitlements Renewals Vulnerabilities Roadmap Health Internally Developed Software Free & Open Source Software Commercial Software
  • 11.
    Thank you foryour attention Questions?

Editor's Notes

  • #2 OSLO staff review