• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Leveraging Open Source
 

Leveraging Open Source

on

  • 2,046 views

Open source applications are rapidly becoming a mainstream option in almost every area of the higher education enterprise. While we are all familiar with the term "open source" at this point, many of ...

Open source applications are rapidly becoming a mainstream option in almost every area of the higher education enterprise. While we are all familiar with the term "open source" at this point, many of us do not really understand the details of how this model is fundamentally different from proprietary software. During this talk, we will discuss what open source really means, how open source licensing works, some of the major benefits of open source software, common myths about open source, where open source is being used in the enterprise, how open source affects the procurement process, and strategies for adopting open source applications into your enterprise.

Statistics

Views

Total Views
2,046
Views on SlideShare
2,042
Embed Views
4

Actions

Likes
2
Downloads
53
Comments
0

2 Embeds 4

http://www.slideshare.net 2
http://www.linkedin.com 2

Accessibility

Upload Details

Uploaded via as OpenOffice

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Leveraging Open Source Leveraging Open Source Presentation Transcript

    • Leveraging Open Source
        • John A. Lewis
        • Chief Software Architect
        • Unicon, Inc.
        • 25 September 2008
        • Brooklyn College, New York
      © Copyright Unicon, Inc., 2008. Some rights reserved. This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/us/
    • What Is Open Source?
      • Lots of Different Terms:
        • Free Software
        • Open Source Software (OSS)
        • Free/Open Source Software (FOSS)
        • Free/Libre Open Source Software (FLOSS)
      • They all mean essentially the same thing
    • Major Organizations
      • Free Software Foundation
        • www.fsf.org
        • Grew out of GNU community
        • Promoters of GNU Public License (GPL)
        • Approves Licenses as “Free Software”
      • Open Source Initiative
        • www.opensource.org
        • Grew out of disagreements with GNU/FSF
        • Less dogmatic / more practical
        • Approves Licenses as “Open Source”
    • Free Or Free?
      • “Free” as if Freedom and Liberty
      • Think Free as in “Free Speech”
      • Not (necessarily) Free as in “Free Beer”
    • What Makes It Free?
      • Major “Freedoms” of Free Software
      • 0: Free to Run
        • Anyone for any purpose
      • 1: Free to Study
        • Access to see and modify source code
      • 2: Free to Redistribute
        • Share binaries and source code
      • 3: Free to Improve
        • Make it better for the whole community
    • Copyright
      • All FOSS licenses based on Copyright
      • Decisions used to be extreme:
        • Complete enforcement - “All Rights Reserved”
        • Put into public domain - “No Rights Reserved”
        • Open Source = “Some Right Reserved”
      • Publisher of open source retains copyright
      • Copyright holder can do whatever they want
        • Do not have to follow terms of their own license
      • Only those who receive software under the license are bound by it
    • Copyleft
      • Requiring software freedom for derivative works based on free software
      • There is no requirement for copyleft in “Free Software” or “Open Source” – Copyleft is a separate concern
      • Two key dimensions:
        • when the copyleft requirements are triggered (usually redistribution)
        • How far the copyleft requirements reach (e.g. source files, compiled together, dynamic linking)
    • Benefits Of Open Source
      • Cost
        • No License Fee
        • Choices about Maintenance / Support
        • No Forced Upgrades
      • Control
        • Pick software and vendor separately
        • Change vendor (or self-support)
        • Change the code - tailor it to your needs
      • Community
        • Collaborate with other users and developers
        • Benefit from the innovation of others
    • Build vs. Buy?
      • Build?
        • Too expensive, takes too long, too risky
      • Buy?
        • Big acquisition cost, vendor lock-in, no flexibility
      • Open Source!
        • Quick and cheap to acquire
        • Adaptable to specific needs
        • Free to choose service provider
        • Leverage community momentum
    • Enterprise Open Source Uses
      • Infrastructure
      • Operating Systems
      • Databases
      • App Servers
      • Web Servers
      • System Monitoring
      • VOIP
      • ... and more
      • Applications
      • Portals
      • Document Mgmt
      • CRM
      • Learning Mgmt
      • Email & Calendaring
      • ... and more
    • Community or Commercial?
      • Community Projects
      • Run by individuals, universities, research groups, etc.
      • Comes out of finding “common cause”
      • Can have commercial providers
      • Linux, Apache, Mozilla, PostgreSQL, uPortal, Sakai, Kuali
      • Commercial Projects
      • Run by a company
      • Build a community
      • Marketing via downloads
      • De facto provider of all value-added services
      • MySQL, Alfresco, Zimbra, SugarCRM, Compiere
    • Who Uses Open Source?
      • Almost everyone!
      • Federal and state governments
      • Colleges and universities
      • Major corporations
      • Small businesses
      • Non-profit organizations
      • Hobbyists
    • Open Source Myths
      • Open Source ...
        • is always more (or less) secure
        • always costs less (or more)
        • is always of better (or lower) quality
        • always has worse documentation
        • is always hard to upgrade
      • It Depends On The Project!
    • Do I Need Developers?
      • No! (biggest myth in higher ed)
      • Major projects all have commercial service providers do handle your needs
      • Same services as proprietary vendors
        • Training, consulting, support, etc.
      • Other services not normally available
        • Customizations, integrations, add/change features, accelerated bug fixes, etc.
      • But you can use your own developers if you want – unique to open source
    • Service Provider Example (aka Shameless Plug)
      • Unicon provides Open Source services primarily to Higher Education
      • Commercial Affiliate for Sakai and uPortal projects
      • Complete range of services:
        • Implementation Planning
        • Project Planning and Assessment
        • Installation / Configuration
        • Branding
        • Training
        • Custom Development / Integration
        • Hosting Services
        • Technical Support
    • Procurement Problems
      • RFI, RFP, travel, demos, proof-of-concepts, pilots, meetings, schmoozing, etc. = High Total Cost Of Sales (TCOS)
      • Example:
        • TCOS is $50K and vendor wins 1 deal in 3
        • Company needs to recover $150K+ on won deals just to cover sales costs!
        • How? High 1 st Year License Fees
      • But Open Source has no license fees!
        • Open Source Vendors cannot respond to RFPs that treat software itself as capital acquisition
    • Viscous Cycle Of Procurement
      • Enterprise procurement has exacerbated this:
      • License fees + switching costs = 5+ years to amortize
      • Must choose carefully = more due diligence
      • Make vendors do the work (at their own expense) = higher TCOS
      • Drives up license fees to recover costs
      • Lather, rinse, repeat...
    • Procuring Open Source
      • Need a new process!
      • No license fees + lower switching costs = lower risks
      • Select the platform yourself (or with help)
        • Separate picking software from picking a vendor
        • Do simple evaluation & pick one or two candidates
        • Do targeted pilot projects to prove they work
      • Spend license fee money on your own people or on services providers for help
    • Questions & Answers John A. Lewis Chief Software Architect Unicon, Inc. [email_address] www.unicon.net