Agenda
• What is open source software and why should you care
• Important trends and best practices in open source
• Evaluating open source software licenses
• Development, implementation, and integration of open
source
Open Source
University of Minnesota
• Open source support
• Questions
01-26-07
University of Minnesota, Open Source
1/26/06
Page 1
University of Minnesota, Open Source
1/26/06
Page 2
Open Source
Agenda
Introduction
• What is open source software and why should you care
“Open source” is the concept of taking an idea,
opening it up to public discussion and developing it
into something that can have a broad benefit to an
entire community.
• Important trends and best practices in open source
• Evaluating open source software licenses
• Development, implementation, and integration of open
source
In its purest sense, it is an open process whose
contributions are made on a voluntary basis and
whose result benefits all.
• Open source support
• Questions
University of Minnesota, Open Source
1/26/06
Page 3
University of Minnesota, Open Source
Definitions on the Web
Definitions on the Web
Open Source
Open Source
• Open source software is similar in idea to "free software" but slightly less rigid
than the free software movement. floss.meraka.org.za/postnukeII/modules.php
• Software that is intended to be freely shared and possibly improved and
redistributed by others.
www.creotec.com/index.php
• Computer software source code that is released under an open-source license or
to the public domain.
www.aardvarkmedia.co.uk/glossary.html
• Any application code that has been made available to developers to view and
modify freely. www.help.thinkhost.com/hosting-related/terminology_212.html
• An open source program has its source code distributed allowing programmers to
alter and change the original software as much as they like.
www.bized.ac.uk/educators/16-19/business/marketing/lesson/sup_glossary.htm
• From: http://www.answers.com/open-source&r=67
www.flinknet.com/summer/28/some-helpful-definitions
• An online interface that allows web site users to submit relevant material to the
web site authors for sharing with other users;
mynasadata.larc.nasa.gov/glossary.html
• Pertaining to software source code that is available to the general public and
does not have licensing restrictions that limit use, modification, or redistribution.
publib.boulder.ibm.com/infocenter/adiehelp/topic/com.ibm.wsinted.glossary.doc/to
pics/glossary.html
• This is a less-confusing name for what is also called 'Free Software'.
www.aleph1.co.uk/armlinux/book/glossary.html
• Information that is publicly available (for example, any member of the public could
lawfully obtain information by request or observation), as well as other
unclassified information that has limited public distribution or access.
www.intelligence.gov/0-glossary.shtml
• A movement in the programming community for making source code (program
instructions) free and freely available to anyone interested in using or working
with it.
www.microsoft.com/technet/prodtechnol/visio/visio2002/plan/glossary.mspx
1/26/06
Page 4
• This is the term that represents virtually the same thing as "free software", only
it's newer, more popular and doesn't have the ambiguity problem.
www.libervis.com/modules/wiwimod/index.php
• In general, open source refers to any program whose source code is made
available for use or modification as users or other developers see fit.
home.comcast.net/~mtsonata/FinalProject/glossary.html
University of Minnesota, Open Source
1/26/06
Page 5
University of Minnesota, Open Source
1/26/06
Page 6
1
Definitions on the Web
Definitions on the Web
Open Source
Open Source Software
• Refers to a basis case where sources of information, code, pictures, maps,
authors, anything likewise, and everything related are all publicly viewable and
openly modifiable. encyclopedia.worldvillage.com/s/b/Open_source
• Open Source Software is software for which the underlying programming code is
available to the users so that they may read it, make changes to it, and build new
versions of the software incorporating their changes.
domainsmagazine.com/managearticle.asp
• Software that is developed, released to and can be modified by the public, free of
charge.
www.eabnet.org.uk/knowitall/finally/glossary/o.htm
• Open source software allows for anyone with programming experience to revise
and change the programming code to suit their individual needs.
www.intensedevelopment.net/website-design-O.html
• Term coined in March 1998 to describe software distributed in source under
licenses guaranteeing anybody rights to freely use, modify, and redistribute the
code. www.slais.ubc.ca/courses/libr500/02-03wt1/www/J_Caldwell/Terminology.htm
• A program in which the source code is available to the general public for use
and/or modification from its original design free of charge, i.e., open.
www.jahadesign.com/glossary.htm
• Free programs created through the collaborative efforts of programmers from
around the world. www.metromemetics.com/thelexicon/o.asp
• Refers to projects that are open to the public and which draw on other projects
that are freely available to the general public.
pedia.nodeworks.com/O/OP/OPE/Open_source/
• Software that shipped with its source code, and that subject to the nine policies of
the Open Source Organisation.
starlab.es/hosting/win/documents/glossary_1_va.html
• Program software of which the code is made available so that implementers may
alter it to meet user requirements.
www.rocksolidsite.com/glossary/I_O.htm
• Open source denotes that the origins of a product are publicly accessible in part
or in whole.
en.wikipedia.org/wiki/Open_Source_Software
• Making the raw, non-compiled code behind a program available to the public for
other programers to analyze, modify, and improve.
www.metromemetics.com/thelexicon/o.asp
University of Minnesota, Open Source
1/26/06
Page 7
University of Minnesota, Open Source
Definitions on the Web
Open Source
Open Source Movement
The Basic Idea
• As per Richard M. Stallman the Open Source Movement was founded in 1998
specifically to reject the idealism of the Free Software Movement. Stallman also
refers readers to one of the GNU sites for further explanation of open source vs.
free software.
www.slais.ubc.ca/courses/libr500/02-03-wt1/www/J_Caldwell/Terminology.htm
1/26/06
Page 8
The basic idea behind open source is very simple:
“When programmers can read, redistribute, and modify the
source code for a piece of software, the software evolves.
People improve it, people adapt it, people fix bugs. And this
can happen at a speed that, if one is used to the slow pace
of conventional software development, seems astonishing.”
• The open source movement is an offshoot of the free software movement that
advocates open-source software as an alternative label for free software,
primarily on pragmatic rather than philosophical grounds.
en.wikipedia.org/wiki/Open_source_movement
Open Source Initiative Organization
(OSI – www.opensource.org)
University of Minnesota, Open Source
1/26/06
Page 9
Open Source History
1/26/06
Page 10
Open Source History: A Timeline
• Started with the concept of
shareware, freeware and
public domain software
• Linux is probably the most
recognizable open source
project
• The term “open source” was
actually coined in February of
1998 according to the Open
Source Initiative Organization
• The concept of free and open
software development
spawned open source hosting
sites such as
SourceForge.com and
FreshMeat.com
• Many projects that are
considered open source
today, actually began well
before the “open source”
movement
University of Minnesota, Open Source
1984
Richard Stallman founds the Free
Software Foundation
1977
CSRG at UC
Berkeley distributes
the first version on
BSD Unix
University of Minnesota, Open Source
1/26/06
Linux 1.0 is release
under the GPL by Linus
Torvalds
1998
Open Source Movement and Open
Source Initiative (“OSI”) founded
1999
Cathedral & the Bazaar published
2003
Linux OS/Apache Web
Server are mainstream
1979
V7 of Unix is
released
• Today there are thousands of
open source projects and
many highly successful
projects
Page 11
Commercially available open
source solution stacks:
integrated, qualified,
supported, distributed, and
evolving
1985
Free Software Foundation (FSF)
develops GNU, a free” version of a
UNIX operating system 1994
1969-1970
Kenneth Thompson, Dennis
Ritchie, and others at AT&T
Bell Labs develop UNIX
Early open development
No business model
Non-profit
1st generation business
model
Packagers: Red Hat,
SUSE
1970s
1980s
1990s
2nd generation business 3rd
3rdgeneration
generation business
business
model
model
model
Professional: MySQL,
OS
OSStacks
Stacks &
& Support
Support
JBoss
options
options
2000 - 2003
University of Minnesota, Open Source
2004 - Present
1/26/06
Page 12
2
Maturity Up and Down the Stack
The Cathedral and the Bazaar
Development
Java, Eclipse, Hibernate, etc.
C, C++, Java
Productivity Tools
Open Office, Firefox, Alfresco
MS Office, IE
• The Cathedral and the Bazaar, by Eric S. Raymond
(http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/)
– Compared to traditional methods (“The Cathedral”*), open source
development (“The Bazaar”*) appears to be disorganized and chaotic.
• Tenants of the Cathedral and Bazaar
App/Web Server
JBoss, Apache, Tomcat
Webspere, Weblogic
MySQL, PostgreSQL, Ingres
Oracle
Snort, SpamAssassin, openSSH
Cisco, SSH
Network Services
Bind, Sendmail, Samba, Nagios
NFS, OpenView, Tivoli, CA
Operating System
Red Hat, Debian, SUSE, Solaris
Microsoft…, Unix…,
Database
Network Security
University of Minnesota, Open Source
1/26/06
– Brooks' Law (The Mythical Man Month) does not apply to Internetbased distributed development
– "Given enough eyeballs, all bugs are shallow"
– Linux belongs to the Bazaar development model
– OSS development model automatically yields the best results
– The Bazaar development model is a new and revolutionary model of
software development
• Can be argued, both in theory and in practice
– A Second Look at the Cathedral and Bazaar, Nikolai Bezroukov
(http://firstmonday.org/issues/issue4_12/bezroukov/)
(http://www.softpanorama.org/Articles/Linux_vs_Solaris/introduction.shtml)
Page 13
University of Minnesota, Open Source
1/26/06
Page 14
Benefits – Why you care
Open Source and Traditional Source
Open Source
Characteristics
• Hybridization and Differentiation
– Linux:
• Tremendous Bazaar development / community
• Tremendous input from the Traditional (IBM, most noteably)
• Further tailored to specific h/w environments by other Traditional
development
•
•
•
•
•
•
•
•
•
•
– JBoss: Hybridized Business Model example
• App server is open source, but the Open Network is not
– Eclipse & Solaris:
• Started in the Traditional
• Pushed into the Bazaar
– Even open Source Lives on a Continuum
• More Pure: Debian, Gentoo, Ubuntu
• More Commercial: Red Hat, Suse, MySQL
• Some open source dual licensed
University of Minnesota, Open Source
1/26/06
Widely successful
No License Fee
Multiple Support Options
Social movement
Power of Community
Technology Choices
Business Choices
Leading Edge Innovation
Worldwide Development
Mainstream Deployment
Page 15
Agenda
•
•
•
•
•
•
•
Reduced Costs
Fosters Agility and Choice
Reduces Time to Market
Adherence to open standards
Simplified Interoperability
Flexibility to Easily Customize
Foundation of Quality Building
Blocks
• Community Support and growth
University of Minnesota, Open Source
1/26/06
Page 16
Today’s Trends
• What is open source software and why should you care
IT Organization
Service Provider
Proprietary/Closed Technology
• Important trends and best practices in open source
• Evaluating open source software licenses
• Development, implementation, and integration of open
source
• Open source support
• Questions
University of Minnesota, Open Source
1/26/06
Page 17
University of Minnesota, Open Source
1/26/06
Page 18
3
Open Source – Analyst Timeline
Open Source – Analyst Timeline Cont.
“Within four years from now we could have more Linux in data centers
than Unix, certainly in Europe.” Also see InformationWeek, for many
panellist's views.
Meta, November 2004
“Consider Linux safe to deploy not only for network edge and simple
Web servers, but also for mid-tier and moderate database applications.”
Gartner Dataquest, November 2005
1/26/06
IDC, July 2006
“Open source software for mission-critical infrastructure and applications
has crossed over from a pioneer or early-adopter status to the point
where it can be considered a mainstream alternative.“
“Linux is the fastest-growing server OS. Linux shipments to increase
from 1.4 million units in 2005 to 2.4 million in 2010, representing a
compound annual growth rate (CAGR) of 11.7 percent.”
Gartner Dataquest, January 2006
University of Minnesota, Open Source
“According to IDC, worldwide open source services spending reached
$4.1 billion in 2005 and will increase to $5.3 billion in 2006 . A growth
rate of 29%. The cumulative opportunity between the beginning of 2005
and the end of 2010 is $46 billion . At a compound annual growth rate
(CAGR) of 23.5% over the next five years.”
Forrester Research, September 2006
Page 19
Open Source – Analyst Timeline Cont.
University of Minnesota, Open Source
1/26/06
Page 20
Open Source Taking Hold
Red Hat Linux
“OSS has significantly penetrated the IT environments of many North
American companies. Gartner Dataquest end-user adoption studies
show that approximately 16% of North American companies use OSS,
and that this usage represents approximately 26% of their overall
software portfolios.“
• Over 2/3 of businesses are planning
a migration of some or all of their
applications from a variety of
systems, including Sun, to Linux
Gartner, November 2006
• By 2009 Linux will be comparable in
penetration directly to Windows and
UNIX
"The amount of venture capital funding invested in the Linux and open
source-related vendors tracked by ComputerWire rose 131% in 2006,
vastly outpacing the IT market as a whole. According to figures collated
by ComputerWire from vendor statements, venture capital companies
ploughed $404.5m into Linux and open source-related vendors in 2006,
compared to $175.1m in 2005."
JBoss
Gartner, November 2006
• 2005 Survey showed JBoss as the
most popular Java application server
University of Minnesota, Open Source
1/26/06
• Linux server shipments will grow to
$10.6B in 2010 at 12% CAGR
Java, Eclipse, Hibernate, etc.
Productivity Tools
Open Office, Firefox, Alfresco
App/Web Server
• #1 ranked product in Forrester’s open
source database Wave in the market
presence category
• IT specialists indicated they deploy
MySQL 30% more frequently than
Oracle, SQL Server or DB2
• In 2005 JBoss Application Server
was moved into the Leaders’
quadrant on Gartner’s Enterprise
Application Server Magic Quadrant
• Evans Data found that MySQL was
the #2 most-used database server
• JBoss moved from Niche to Visionary
to Leader in under 24 months
• Over 6,000,000 installations; 50,000
downloads/day
• Founded in 1995; operations in 19
countries
Page 21
University of Minnesota, Open Source
1/26/06
Page 22
1/26/06
Page 24
Open Source Growth
Worldwide Services by Segment
Maturity Up and Down the Stack
Development
MySQL
Worldwide Open Source Services Revenue by Segment
2005 - 2010
12000
10000
JBoss, Apache, Tomcat
23.8% Overall 2006-2009 CAGR
3X average server IT Market growth
8000
Database
MySQL, PostgreSQL, Ingres
Network Security
Snort, SpamAssassin, openSSH
Network Services
Bind, Sendmail, Samba, Nagios
Operating System
Red Hat, Debian, SUSE, Solaris
6000
4000
2000
0
2005
Consulting
2006
2007
Implementation
2008
Support
2009
Outsourcing
2010
Training
IDC, July, 2006
University of Minnesota, Open Source
1/26/06
Page 23
University of Minnesota, Open Source
4
Open Source Growth
U.S. Services by Segment
Open Source Trends: Survey
Respondent Phase Of Adoption
U.S. Open Source Services Revenue by Segment,
2005 - 2010
6000
5000
54.4%
53.2%
Question: At what stage is your company at
in considering or adopting open source
software?
North America N = 103
20.3% Overall 2006-2009 CAGR
3X average server IT Market growth
Europe N = 124
25.2%
9.7%
3000
4.0% 4.9%
17.7%
15.3%
10.7%
4000
4.9%
2000
We are
planning to pilot
or adopt
1000
0
2005
2006
Consulting
2007
2008
Implementation
2009
Support
We are
currently
piloting
We have
We are
evaluated open interested in
source and
open source,
decided not to
but with no
adopt now
current plans
2010
Outsourcing
Training
North America
IDC, July, 2006
Currently using
Europe
Forrester Research, 2006
University of Minnesota, Open Source
1/26/06
Page 25
University of Minnesota, Open Source
1/26/06
Page 26
1/26/06
Page 28
Governments and Commercial OSS
View
Government ambitious on OSS
University of Minnesota, Open Source
1/26/06
Page 27
Perceived Inhibitors to Open Source
University of Minnesota, Open Source
Perceived Benefits of Open Source
Company Policy
Lack of Support Services
No Skills to Develop/ Integrate
Low Acquisition Cost
Support Services Inadequate
Low Total Cost of Ownership
Quality of OSS Components
Hardware Choice, including low-cost Intel Servers
Lack of Applications or Functionality
Better Security
IP/Ownership Issues
Software Choice, Including Alternate Suppliers
Maintenance of OSS Components
Familiar to Developers/We have the Skills
Management of OSS Licenses
Higher Quality
Difficult to Source Components
Other
Other
0
Source: User Survey Report: Open-Source and Linux Software
Support Services, North America, 2006; Gartner, July 2006
5
10
15
20
0
Percentage of Respondents
20
40
60
80
100
Percentage of Respondents
Source: Forrester Research, June 2005
University of Minnesota, Open Source
1/26/06
Page 29
University of Minnesota, Open Source
1/26/06
Page 30
5
Open Source
Evolution
Research Estimates for the Market
Gartner research
shows strong trends to
replace proprietary
RDBMS with OSS
RDBMS:
•70% in North America
• 60% in Europe
Industries
ƒ
ƒ
ƒ
ƒ
ƒ
Government
Infrastructure
Scientific/HPC
ISPs
Universities
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
Government
Infrastructure
Scientific/HPC
Telco / ISPs
Universities
Retail (POS)
Finance (risk management)
Banking (portfolio analysis)
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
Government
Infrastructure
Scientific/HPC
Telco
Universities
Retail (POS)
Finance (risk management)
Banking (portfolio analysis)
Travel (reservations)
Media and Entertainment
Digital content creation
Aerospace (analysis applications)
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
Government
Infrastructure
Scientific/HPC
Telco
Universities
Retail (POS)
Finance (risk management)
Banking (portfolio analysis)
Travel (reservations)
Media and Entertainment
Digital content creation
Aerospace (analysis applications)
Economic
Value
ƒ
ƒ
ƒ
ƒ
Price/Performance
Lower TCO
Simplified Systems Management
Improved Time to Market
ƒ
ƒ
ƒ
ƒ
Price/Performance
Lower TCO
Simplified Systems Management
Improved Time to Market
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
Price/Performance
Lower TCO
Simplified Systems Management
Improved Time to Market
High Reliability
Open platform/foundation
Reusability/flexibility
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
Price Performance
Lower TCO
Simplified Systems Management
Improved Time to Market
High Reliability
Open platform/foundation
Reusability/Flexibility
Better Levels of Service
Increased IT utilization
• 40% in Latin America
ƒ Implementation Services
Services
ƒ Implementation Services
ƒ Consulting Services
• 50% APAC
Overall OS RDBMS
market growth of 100%
over next two years
Primary
Open Source
In Use
ƒ E-mail Servers
ƒ DHCP
ƒ BIND / DNS
ƒ Scientific HPC
ƒ
ƒ
ƒ
ƒ
ƒ
Linux
Apache
MySQL
PHP
AXIS Web Svc
Edge
Infrastructure
ƒ
ƒ
ƒ
ƒ
ƒ
JBoss
PostgreSQL
Firefox
Python
Perl
Static Web
Infrastructure
ƒ Implementation Services
ƒ Consulting Services
ƒ Application Architecture Services
ƒ Implementation Services
ƒ Consulting Services
ƒ Application Architecture
ƒ Business Innovation Services
ƒ Enterprise Applications
(CRM, SCM, ERP)
ƒ LAN/WAN (ethereal, Nagios Sys.
Management)
ƒ Office Products (Open Office, Open
Workbench)
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
Application
Serving
2000-2004
University of Minnesota, Open Source
1/26/06
Enterprise Integration
Partner Integration
Dynamic Business Models
Business Intelligence
E. Content Management
Collaboration
SOA
Security
Line of Business
Solutions
2005
Page 31
University of Minnesota, Open Source
2006
1/26/06
Page 32
Trends
Conclusions
Strong Momentum & Industry Support
• Open source in commercial
deployments has grown greatly
• Forecasts / Analysts expect this trend
to continue and flourish
Unisys
Open Source
Adoption
Is Real
• Open Source projects have matured
such that they can compete directly
with commercial offerings
• Concerns exist, but are addressed by
services
• Open source usage continues to
increase.
• Open source is no longer confined to
data center technology.
• Open source companies have value.
• There is serious investment in open
source
University of Minnesota, Open Source
1/26/06
Page 33
University of Minnesota, Open Source
Best Practices
Best Practices
Open Source Development Roles
Open Source Reality
Users
Bugsubmitters
Page 34
• All open source projects have an owner
Contributors
Documenters
1/26/06
Graphic
Artists
• Anyone can participate in open source regardless of their
skill level or technical knowledge
Translators
• Volunteers may actually be paid by a third party to
participate in an open source project
Developers
• Results can be freely used by the entire community
Coders
Maintainers
Tool
Builders
Porters
• Results may be used to generate revenue directly or
indirectly
GUI
Designers
University of Minnesota, Open Source
1/26/06
Page 35
University of Minnesota, Open Source
1/26/06
Page 36
6
Best Practices
How You Can Participate…
Benefits of open-sourcing software
• Submit source code patches
• Promote the use of open
source software
• Gain visibility and recognition by the community, be seen as an
innovator and expert to go to for services and support
• Evaluate open source
software for use within your
environment
• Build confidence and trust of the community & target audience
• Submit documentation
patches
• Review code or
documentation
• Test open source software
• Ask questions
• Provide feedback
– Submit bug reports
– Suggest enhancements
• Understand the shared set of requirements and gain insights into
needs directly from end-users: invaluable market data
• Suggest ways that your
technology could be used to
enhance open source
software (upon approval)
• Standardize on agreed common criteria for technology
architecture, component set and solution deliverables
• Influence direction and technology choices as a contributor
• Lower costs of development, testing & support
• Or, just use it
• Build the basis for a support knowledgebase for the end-users
– Provide support
University of Minnesota, Open Source
1/26/06
Page 37
University of Minnesota, Open Source
1/26/06
Page 38
Best Practices
Secret to Success
Agenda
• How to succeed in the open source community:
• What is open source software and why should you care
– Relationships
– Relationships
– Relationships
• Important trends and best practices in open source
• Evaluating open source software licenses
• Development, implementation, and integration of open
source
• Form good relationships through consistent participation,
contributions and acknowledgements
• Open source support
• Once relationships have been established, treated them as
valuable assets
University of Minnesota, Open Source
1/26/06
• Questions
Page 39
University of Minnesota, Open Source
1/26/06
License Agreements
License Agreements Continued
• All open source code is protected by some type of license agreement
• Before making use of any open source code, make sure that the license
agreement is understood and complies with the intended use
• License defines the condition under which the source code may be used
and obligations with respect to enhancements and derivative works
• No permission needed if software is in the “public domain” (i.e.,
no one claims rights in it) - very rare
• There are a number of approved open source license agreements
(www.opensource.org/licenses)
• Most commonly used licenses – GPL, LGPL, BSD, MIT, and Mozilla
• Careful not to confuse open source, freeware and shareware
software with public domain software
• Does not have to be one of the approved license agreements
• Open source and “free” are often used in the same sentence
• The license agreement must adhere to the official open source definition
(www.opensource.org/docs/definition.php)
• Open source “free” actually means freely available and
redistributable, within the constraints of its license
• Some license agreements allow free and open use of the software and
source code – others are much more restrictive
University of Minnesota, Open Source
1/26/06
Page 40
• Open source can have dual licenses, one that is open source,
and another that is commercial
Page 41
University of Minnesota, Open Source
1/26/06
Page 42
7
Open Source Initiative (OSI)
License Definition
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
• The Open Source Initiative, a non-profit entity dedicated to managing and promoting
open source, currently has listed ten required elements of the open source definition.
59 OSI Approved
Licenses
• (See http://www.opensource.org/docs/definition_plain.php)
ƒ
ƒ
ƒ
5. No Discrimination Against Persons or Groups
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
6. No Discrimination Against Fields of Endeavor
ƒ
1. Free Redistribution
2. Source Code
3. Derived Works
4. Integrity of The Author's Source Code
7. Distribution of License
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
8. License Must Not Be Specific to a Product
9. License Must Not Restrict Other Software
10. License Must Be Technology-Neutral
University of Minnesota, Open Source
1/26/06
Page 43
Choosing an Open
Source License
Step One*:
Do you want people to be
able to take modifications
private or not?
• If you want to get the source
code for modifications back from
the people who make them,
apply a license that mandates
this.
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
Workspace License (CVW License)
Motosoto License
Mozilla Public License 1.0 (MPL)
Mozilla Public License 1.1 (MPL)
NASA Open Source Agreement 1.3
Naumen Public License
Nethack General Public License
Nokia Open Source License
OCLC Research Public License 2.0
Open Group Test Suite License
Open Software License
PHP License
Python license (CNRI Python
License)
Python Software Foundation
License
Qt Public License (QPL)
RealNetworks Public Source
License V1.0
Reciprocal Public License
Ricoh Source Code Public License
Sleepycat License
Sun Industry Standards Source
License (SISSL)
Sun Public License
Sybase Open Watcom Public
License 1.0
University of Illinois/NCSA Open
Source License
Vovida Software License v. 1.0
W3C License
wxWindows Library License
X.Net License
Zope Public License
zlib/libpng license
University of Minnesota, Open Source
Step Two*:
Do you want to allow
someone to merge your
program with their own
proprietary software?
* From The Open Source Definition by Bruce Perens
1/26/06
Page 44
• If so, use the LGPL, which
explicitly allows this without
allowing people to make
modifications to your own code
private, or use the X or Apache
licenses, which do allow
modifications to be kept private.
* From The Open Source Definition by Bruce Perens
University of Minnesota, Open Source
1/26/06
Page 45
Choosing an Open
Source License
Do you want some people
to be able to buy
commercial-licensed
versions of your program
that are not open source?
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
Choosing an Open
Source License
• The GPL and LGPL would be
good choices. If you don't mind
people taking modifications
private, use the X or Apache
license.
Step Three*:
Academic Free License
Adaptive Public License
Apache Software License
Apache License, 2.0
Apple Public Source License
Artistic license
Attribution Assurance Licenses
New BSD license
Computer Associates Trusted Open
Source License 1.1
Common Development and
Distribution License
Common Public License 1.0
CUA Office Public License Version
1.0
EU DataGrid Software License
Eclipse Public License
Educational Community License
Eiffel Forum License
Eiffel Forum License V2.0
Entessa Public License
Fair License
Frameworx License
GNU General Public License (GPL)
GNU Library or "Lesser" General
Public License (LGPL)
Historical Permission Notice and
Disclaimer
IBM Public License
Intel Open Source License
Jabber Open Source License
Lucent Public License (Plan9)
Lucent Public License Version 1.02
MIT license
MITRE Collaborative Virtual
University of Minnesota, Open Source
1/26/06
Page 46
Choosing an Open
Source License
• If so, dual-license your software.
I recommend the GPL as the
open source license, you can find
a commercial license appropriate
for you to use in books like
copyright your software from
NoloPress.
Step Four*:
Do you want everyone who
uses your program to pay
for the privilege?
* From The Open Source Definition by Bruce Perens
• If so, perhaps open source isn't
for you. If you're satisfied with
having only some people pay
you, you can work that and keep
your program open source. Most
of the open source authors
consider their programs to be
contributions to the public good,
and don't care if they are paid at
all.
* From The Open Source Definition by Bruce Perens
University of Minnesota, Open Source
1/26/06
Page 47
University of Minnesota, Open Source
1/26/06
Page 48
8
Agenda
AS-IS to TO-BE: Toward Open…
Application, Asset Silos
• What is open source software and why should you care
Open & Service Oriented Applications
& Assets
• Important trends and best practices in open source
New Business Processes
• Evaluating open source software licenses
Business Services
• Development, implementation, and integration of open
source
• Open source support
Business
Logic
Business
Logic
Business
Logic
Business
Logic
Business
Logic
Business
Logic
Business
Logic
Business
Logic
LEGACY
ERP
CRM
FINANCE
LEGACY
ERP
CRM
FINANCE
• Questions
Business functionality buried in applications,
asset silos … proprietary interfaces serving
the silos
University of Minnesota, Open Source
1/26/06
Page 49
Business functionality exposed as business
services … standards-based, shared & reusable
services
University of Minnesota, Open Source
1/26/06
Page 50
Comprehensive – Consider all layers
of the business
What enables Open?
Business Vision & Strategy
to meet enterprise objectives
• Open Architecture Objectives – well-planned IT
– Service Oriented
– Component Oriented
– Model Driven
Business Processes
that enable your vision
• Open Standards – industry cooperation
– Agreed upon way to solve a problem
– Standard interfaces and behaviors
– Implementations by commercial vendors and open source
community
Applications & Information
to automate key aspects
of your business
• Open Source – a delivery model
– No-cost license
– Ability to access and contribute to the source code
– Often implements or drives the development of standards
University of Minnesota, Open Source
Infrastructure
that provides the secure
foundation for high value delivery
1/26/06
Page 51
Potential Evaluation Parameters
Business Vision & Strategy
Business Process
ƒ
ƒ
ƒ
Compliance with overall PSI
strategy
Compliance with political
priorities
Compliance with IT goals
and targets
Openness
ƒ
ƒ
ƒ
ƒ
Functional fit with existing
business processes
Flexibility in supporting specific
business processes
Support of workflows
Information infrastructure
Customizable
Independent from vendor
Knowledge sharing
Supporting organizational
evaluation
Legal evaluation
ƒ
ƒ
ƒ
ƒ
Internal/external resources
Community evaluation
Legal evaluation
Code management capacity
ƒ
ƒ
Effect on business processes
Possibility of optimizing business
processes
Learning costs
Process change costs
ƒ
ƒ
ƒ
ƒ
ƒ
• Questions have shifted from "if" and "whether" to "where best" and "how best."
Licenses
Updates and maintenance
Cost of security breaches
Migration costs
Scalability
ƒ
ƒ
Costs from hardware
requirements
Costs from future hardware
requirements
Functional Evaluation
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
General flexibility in application
Possibility of individualization
Security
Standards based
User friendliness
Information infrastructure
Reliability
ƒ
ƒ
ƒ
ƒ
Standards based
Compliance with present
hardware setup
Impact on future hardware
decisions
HW performance
Additional Evaluation
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
Page 52
Infrastructure
TCO Evaluation
Support costs
Implementation costs
Long term time consumption
Scalability
1/26/06
Best Practices
Applications & Information
ƒ
ƒ
ƒ
ƒ
University of Minnesota, Open Source
Future proof?
Market trends
Reputation
Code Management capacity
Interoperability
ƒ
ƒ
Compliance with hardware
strategy
Interoperability
• Policies and processes governing open source deployments must be designed, maintained,
and refined in ways that focus on maximum business value and on close integration with IT
infrastructures, personnel, and other resources.
• Consistent, consolidated, integrated management of closed and open source solutions is
essential to achieving sustained levels of availability and performance, and to maximizing
business value and operational agility.
• Best practices involve directly addressing
–
–
–
–
–
–
Selection
Sourcing
Integration
Policy-based management
Risk mitigation
Support
• Select management tools that provide equally strong support for open and closed source
solutions
• Leverage Tools and Vendors to augment your strengths and weaknesses
• Align with trusted partners that have proven experience and expertise
University of Minnesota, Open Source
1/26/06
Page 53
University of Minnesota, Open Source
1/26/06
Page 54
9
Open Architecture
Open Architecture
Journey
Journey
Agile Enterprise Goal
Agile Enterprise
Continuity
Implementation
Enablement
Governance
Validation
Planning
Envisioning
Today
Today
1/26/06
Establish General Objectives leveraging Open
technologies
Rules Of Engagement
• Understand the Big Picture and where you need to be
• Do
–
–
–
–
–
–
• Gain Open experience with in a non-critical area first
• Build on existing core applications and processes
1/26/06
Page 56
Risk/reward analysis of license for each file, port, or download (item)
Establish centralized control structure
Secure management approval for each item licensed
Document approval of each separate item
Comply with all license terms
Feel free to experiment
• Don’t
• Use off-site facilities to avoid conflict with production
systems
–
–
–
–
• Use expert skills to supplement your own
University of Minnesota, Open Source
Business Analysis
Training on Open concepts
Interviewing
University of Minnesota, Open Source
The Move to Open Source is a Journey
• Identify the steps that make up the Journey
Requirements Mgmt
Roadmap, Project Schedule
Where you are today…
Page 55
• Know where you are today
Testing Vendor claims
Legal Reviews
Define Current State of enterprise
Assessment
Envisioning
Identify where you want to be
University of Minnesota, Open Source
Plan to address Gap, establish Open
Adoption Plan
Planning
Where you are today…
Roles Assessment
Tooling
Reduce Risk and ways to reduce total
cost of ownership
Validation
Understand where you are & what you are capable of
Retooling, Training,
Infrastructure
Establish roles, rules of
engagement & lifecycle mgmt
Governance
Plan for lifecycle management
Eliminate Risk and understand costs
Upgrades
Regression
Refactoring, Coding
Application Modernization
Ensure that the
organization is ready
Enablement
Create a plan to bridge the gap
Assessment
Iterative execution of
the Open plan
Implementation
Execute the plan
Ensure everything is in place
Activities
Maintain stability as
changes occur
Continuity
Continuous improvement
1/26/06
Short cut the process
Act as your own lawyer
Incorporate any ‘free’ code without documenting it
Merge new code with ‘free’ code if possible
Page 57
University of Minnesota, Open Source
Agenda
Types of Open Source Solutions
• What is open source software and why should you care
• Components or Frameworks
1/26/06
Page 58
– Reusable pieces of code
• Important trends and best practices in open source
– Embedded in other Open Source OR Proprietary solutions
(depending on License)
• Evaluating open source software licenses
• Standalone Solutions
• Development, implementation, and integration of open
source
– Complete, end-to-end product-like solution
– Adheres to, or is a standard, referenceable implementation
– Supported (3rd party, community, or sponsor)
• Open source support
• Questions
• Complete Solution (Integrated open source stacks)
– Together with proprietary software
– Open Source components as “glue”
University of Minnesota, Open Source
1/26/06
Page 59
University of Minnesota, Open Source
1/26/06
Page 60
10
Open Source Support & Services
Competition and Options
Unisys Open Support Services
Ver 1.0
The complexity and cost
of managing stack
component releases,
patches and revisions can
be significant
Much of open source is
built upon other open
source
JBoss
NET
Web Services
Security
Web
Admin, Mgmt,
/Messaging
JBoss
WS4EE
JVM
O.S.
Platform
Platform
JBoss
WS
Application Defender
Application Defender
1.0
1.1
2.0
s
os
JB Q
M
Admin Console
1.1
JBoss
s g
Sys Mgmt.
os
1.0
JB agin JBoss
Admin Console
ss Admin Console
1.1
JBoss ON Me
JBoss ON
Oracle
PostgreSQL
MySQL
Oracle
PostgreSQL
MySQL
Oracle
9i (32-64 bit)
8.1.2 (32bit)
4.1.16
10g (64 bit)
8.1.x
4.X or 5.x
10g (64 bit)
TomCat
3.2.6
s
os
JB Q
M
5.0
JBoss
TomCat
4.0.3 SP1
5.5
JBoss
4.X or 5.0
JVM
JVM
JVM
JVM
JVM
1.4.2 32-bit
1.4.2 64-bit
1.4.2_10 (32 bit)
1.4.2_10 (64 bit)
5.0
SLES9
32-64 bit
RHEL4
32-64 bit
Gallatin
IA64, IA32
OSS consulting,
deployment and
migration
services
Ver 3.0
Application Defender
Database
Netwo
JBoss
rk
Consulting & Integration
Ver 2.0
SLES9
X86 64
RHEL4
U3 X64
EM64T
EM64T
5.5
Ideal: Full
support,
consulting
and services
7x24 consulting, maintenance
and vertically integrated
solutions support, systems
integration, including custom
solutions. Resources and ability
to drive projects to completion.
RHEL4
U3 X64
SLES9
X86 64
X64
Potomac Paxville
TomCat
Life Cycle Services
X64
Itanium
Paxville
IA64
EM64T
Traditional SIs
Ind. Std. Servers
OS Vendor Support
OS Solution/Stack Support
Subscription packages for plug-nplay convenience with enterprise
support options
Integrated Stacks
+
University of Minnesota, Open Source
Knowledgebase
Capabilities to certify, test and integrate a wide portfolio of OSS applications, including the possibility
of a knowledge base with rules for compatibility or reference architectures that can automatically
detect incompatibilities among versions and libraries from a multiplicity of OSS applications.
1/26/06
Page 61
OSS
certification
testing and
integration
University of Minnesota, Open Source
1/26/06
Page 62
University of Minnesota, Open Source
1/26/06
Page 64
Agenda
• What is open source software and why should you care
• Important trends and best practices in open source
• Evaluating open source software licenses
• Development, implementation, and integration of open
source
• Open source support
Questions?
• Questions
Thanks.
University of Minnesota, Open Source
1/26/06
Page 63
11