1.
Introduction to Open Source
License and Business Model
ANOverviewof thehistory of OpenSourcemovement,
Licenses and culture; and Thecommunity architecture
thatdrivestheecosystem

2.
(c) 2018 kagesenshi.org Page 2 / 24
About Me
●
Mohd Izhar Firdaus Bin Ismail
●
Head Data Engineering Department & Solution Architect, ABYRES
Enterprise Technologies Sdn Bhd
●
Fedora Ambassador, Open Source Advocate & Contributor, Python
Programmer, Cybersecurity Enthusiast
– Open source contributor since 2005
●
Regional Fedora treasurer until 2017
– Contributes code to multiple projects:
●
Fedora – RPM packages and bugfixes
●
Plone – python based CMS / DMS
●
Morepath – python web framework
●
Obviel – javascript web framework
●
Various patches here and there
– Contributes to HackInTheBox Security Conference
●
CTF scoreserver developer
– Organizers in multiple FOSS events:
●
Core organizer of FOSS.My 2008 & 2009
●
Main organizer of Fedora User Developer Conference KL 2012
●
Assisting in pycon.my, geekcamp KL, barcamp KL
– Given talks in various community events like FUDCon Pune, FUDCon Phnom
Penh, HITB CommSec, multiple hackathons and barcamps, etc

3.
(c) 2018 kagesenshi.org Page 5 / 24
Disclaimer
I Am Not A Lawyer
However I have been in Open Source world long enough and deep enough to understand the legal nature
of the licenses and the architecture of the communities in the global platform
That said, information about software licenses in this session does not constitute a certified legal advise on
intellectual property laws, as the laws may vary across countries.

4.
(c) 2018 kagesenshi.org Page 6 / 24
EarlyDaysof Software Development
●
In the 1950s and 1960s, computer operating
software and compilers were delivered as a part of
hardware purchases without separate fees.
– source code, the human-readable form of software,
was generally distributed with the software providing
the ability to fix bugs or add new functions.
●
Universities were early adopters of computing
technology.
– modifications developed by universities were openly
shared, in keeping with the academic principles of
sharing knowledge
– origins of the 'hacker culture' – group of people,
sharing knowledge on specific technological domains
●
Software were not copyright-able until 1974
●
In the late 1970s and early 1980s computer
vendors and software-only companies
began routinely charging for software
licenses, marketing software as "Program
Products"
– imposing legal restrictions on new software
developments, now seen as assets, through
copyrights, trademarks, and leasing
contracts

5.
(c) 2018 kagesenshi.org Page 7 / 24
richardM.Stallman, Father of Free Software Movement
●
Drawing on traditions and philosophies among members of
the 1970s hacker culture and academia
– Richard M. Stallman, a researcher at MIT AI labs founded the
GNU Project and Free Software Foundation (FSF)
●
Free Software Philosophy:
– Rejecting proprietary software, with ultimate goal of liberating
everyone in cyberspace
– Stallman notes that this action will promote rather than hinder the
progression of technology
●
"it means that much wasteful duplication of system programming
effort will be avoided. This effort can go instead into advancing the
state of the art"
– 'Free' as in Freedom, not free as in free beer teh tarik
●
Four Freedoms
– Freedom 0: Use
– Freedom 1: Study
– Freedom 2: Share
– Freedom 3: Improve

6.
(c) 2018 kagesenshi.org Page 9 / 24
Four Freedomsof FreeSoftware &GNU General Public License
●
'Free' as in Freedom, not free as in free beer teh tarik
●
Four Freedoms of Free Software
– Freedom 0: Use
●
The freedom to run the program as you wish, for any purpose
– Freedom 1: Study
●
The freedom to study how the program works, and change it
so it does your computing as you wish
●
Access to the source code is a precondition for this.
– Freedom 2: Share
●
The freedom to redistribute copies so you can help your
neighbor
– Freedom 3: Improve
●
The freedom to distribute copies of your modified versions to
others.
●
By doing this you can give the whole community a chance to
benefit from your changes.
●
Access to the source code is a precondition for this.
●
To enforce protection of the Four Freedoms, FSF
and Stallman created a software license called
GNU General Public License (GPL), which
– Riding on top of copyright law, uses copyright as a
way to allow and enforce freedom instead of limiting
freedom, a.k.a "Copyleft"
– GPL allows software authors to license out their
software and source code to anybody, where:
●
The four freedoms are granted to the licensee
●
With the condition that the licensee must ensure the four
freedom rights are retained for downstream licensees
●
The licensee must ensure that the four freedoms are
given on their modification of the software by releasing
the modifications under the GPL too

7.
(c) 2018 kagesenshi.org Page 10 / 24
OpenSource Initiative
●
On 1998, Jon "maddog" Hall, Larry Augustin, Eric S.
Raymond, Bruce Perens, Michael Tiemann, and others
created the term "Open Source" and started up the
Open Source Initiative (OSI)
– OSI chose the term "open source," in founding member
Michael Tiemann's words, to "dump the moralizing and
confrontational attitude that had been associated with
'free software'" and instead promote open source ideas
on "pragmatic, business-case grounds."
●
OSI adopted the "Open Source Definition" to define
what software and software licenses constitute as
Open Source

8.
(c) 2018 kagesenshi.org Page 11 / 24
OpenSource Software Definition
●
A software which are licensed under a license that guarantees the following rights
– Free Redistribution
●
The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution
containing programs from several different sources. The license shall not require a royalty or other fee for such sale.
– Source Code
The program must include source code, and must allow distribution in source code as well as compiled form. Where some form of a
product is not distributed with source code, there must be a well-publicized means of obtaining the source code for no more than a
reasonable reproduction cost, preferably downloading via the Internet without charge. The source code must be the preferred form in
which a programmer would modify the program. Deliberately obfuscated source code is not allowed. Intermediate forms such as the
output of a preprocessor or translator are not allowed.
– Derived Works
●
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of
the original software.
– Integrity of The Author's Source Code
●
The license may restrict source-code from being distributed in modified form only if the license allows the distribution of "patch files" with
the source code for the purpose of modifying the program at build time. The license must explicitly permit distribution of software built
from modified source code. The license may require derived works to carry a different name or version number from the original
software.

9.
(c) 2018 kagesenshi.org Page 12 / 24
OpenSource Software Definition
– No Discrimination Against Persons or Groups
●
The license must not discriminate against any person or group of persons.
– No Discrimination Against Fields of Endeavor
●
The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the
program from being used in a business, or from being used for genetic research.
– Distribution of License
●
The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional
license by those parties.
– License Must Not Be Specific to a Product
●
The rights attached to the program must not depend on the program's being part of a particular software distribution. If the program is
extracted from that distribution and used or distributed within the terms of the program's license, all parties to whom the program is
redistributed should have the same rights as those that are granted in conjunction with the original software distribution.
– License Must Not Restrict Other Software
●
The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license
must not insist that all other programs distributed on the same medium must be open-source software.
– License Must Be Technology-Neutral
●
No provision of the license may be predicated on any individual technology or style of interface.

10.
(c) 2018 kagesenshi.org Page 13 / 24
FreeSoftware& Open Source DoesNot MeanNoCopyright
●
Free & Open Source Software (FOSS) are
copyrighted and not public domain
– The author retains the copyright and intellectual
property, however, the author choose to grant
licensee of the software additional rights which
normally are not granted under proprietary license
– Any users of the software automatically become the
licensee the moment they acquire a copy of the
software
– FOSS authors usually will re-use legal license
documents already exist in the FOSS community as
the license for his software.
●
GPL, AGPL, MIT License, BSD License, Apache
License, CDDL, WTFPL, etc
●
Should you not comply with terms and conditions in
the license document, the author have the rights to
enforce the license terms or sue you

11.
(c) 2018 kagesenshi.org Page 14 / 24
Types OfOpen Source Licenses
PermissiveWeak CopyleftStrong Copyleft
●
Most flexible
●
Derivative works are not
required to be Open
Source or using the
same license
●
Only requires attribution
that the portion of the
code was taken from the
author
●
eg: MIT, BSD
●
Some parts of derivative
works are required to be
using the same license
●
Usually this license is
used on a library
●
Modifications to itself are
required to be released
under same license, but
projects importing the
library are not required
to be using same license
●
eg: LGPL
●
Strict enforcement of
same license for any
derivative works
●
All projects importing
libraries provided by
software licensed under
this license are required
to be also released
under the same license
of the original work
●
eg: GPL, AGPL

12.
(c) 2018 kagesenshi.org Page 15 / 24
How DoOpen Source DevelopersMakeMoney?
●
In Open Source ecosystem, the software is free, but
human time is not
●
Services is the primary method of earning in Open
Source ecosystem
– Services:
●
Software development
●
Implementation & integration services
●
Consulting
●
Training
– Service subscriptions:
●
Support & warranty
●
Software As A Service
●
Platform As A Service
●
Infrastructure As A Service
●
Managed Services
●
Managed Operations
– OpenCore:
●
Core software is open source, but selling proprietary plugins
and management tools

13.
(c) 2018 kagesenshi.org Page 16 / 24
OpenSource Development &Consumption Model
Independent
Developers
Community
Source Code
Repository
Trusted
Developers
Enterprise
Developers
Enterprise Fork
Source Code
Repository
Enterprise
Executables
Enterprise Users
Source code Source code
Problem Reports & Code Enhancements
Enterprise
Support
Stable source code
& enhancements
Problem Reports
Problem Reports
& Support Requests
Upstream Community
Enterprise Product
Company
Upstream
Executables
Build
Distribute
Build
Community Users
DistributeProblem
Reports
This chain may extend further downstream,
where organizations pick up source code from
enterprise companies to create derivative
works
Community
Support Forum
Support Requests
Support
Support

14.
(c) 2018 kagesenshi.org Page 17 / 24
OpenSource ValueChain
Software developed in
public, possibly with
community contribution,
and many frequent
improvements
Enterprise software distribution /
product company takes a
snapshot of codebase, stabilize,
integrate, create support, training
and warranty model, and
productize the software
Enterprise customer buys
productized software, and receive
support, training, and warranty
from distribution company and
services from SI
Ecosystem of System Integrator,
ISV, trainers provide professional
services and added value for
using the productized software

15.
(c) 2018 kagesenshi.org Page 18 / 24
UpstreamSoftware Vs DownstreamEnterprise Product
Upstream Enterprise
●
Rapid changing
●
Latest and greatest
features
●
Can be unstable
●
No warranty, no
support, or minimally
supported
●
Most of time free of
capital cost
●
Less changes over
short period of time
●
Tried and tested
features
●
Generally more stable
●
Comes with warranty,
support SLA, training
and certifications
●
Charged for support &
warranty subscriptions
and professional
services

16.
(c) 2018 kagesenshi.org Page 19 / 24
Other Communities
(Community)
Fedora Project
(Community)
Red Hat
(Company)
CentOS Project
(Community)
Linux Foundation
(Community)
Free Software Foundation
(Community)
CaseStudy: Fedora,RedHat, OracleEL &CentOS
Linux Kernel
GNU Utilities
Hundreds of Open
Source Software
Fedora Linux
Red Hat Enterprise
Linux
CentOS Linux
Every 3 years a snapshot of
Fedora is stabilized by Red Hat
to create next version of RHEL
CentOS community picks up RHEL
source code immediately after
release, removes branding, and
builds CentOS from the source code
(usually 1-2 months after official
RHEL release)
Fedora Project collects,
packages and integrates
various Open Source Software
into an integrated software
distribution
Rogue Wave
(Company)
Abyres
(Company)
Alongside community level
support through public forums,
CentOS is also commercially
supported by many FOSS
support providers
Oracle
(Company)
Oracle Linux
Similar to CentOS, Oracle picks up RHEL source
code, removes branding, and builds Oracle Linux
from the source code. Oracle Linux adds Oracle
database specific optimization in its distribution

17.
(c) 2018 kagesenshi.org Page 20 / 24
Evolution ofRHL, RHEL,Fedora, Centos
Red Hat Linux
Red Hat Enterprise Linux
Around 2002/2003, Red Hat decided
to split Red Hat Linux 9 into 2
separate distribution, where one
distribution would be community led
and another controlled by RH.
Fedora Linux was created to allow community
to rapidly add enhancements and innovations
on top RHL codebase without the corporate
control of Red Hat. A new Fedora release is
created every 6 months by the community.
Red Hat Enterprise Linux was
created to provide a very stable base
for Red Hat enterprise customers,
where RH controls what goes into the
distribution
Every 3 years a snapshot of
Fedora is stabilized by Red Hat
to create next version of RHEL
CentOS was founded to cater to
the need in the community for a
stable (ie: slow changing),
community enterprise OS which
Fedora does not provide
Today CentOS is used by Red
Hat as the platform for their
middleware and cloud stack
layer community innovation to
happen (eg: Openshift,
Openstack, etc) because for
development of cloud stack
layer softwares, Fedora moves
a bit too fast.

18.
(c) 2018 kagesenshi.org Page 21 / 24
Hortonworks
(Company)
Apache Foundation
(Community)
CaseStudy:Hadoop, Hortonworks& Cloudera
Hadoop Project
Hortonworks
Data Platform
Spark Project
Sqoop Project
Other Hadoop
Distribution
Components
Cloudera
(Company)
Cloudera
Data Hub
Microsoft
(Company)
HDInsights
IBM
(Company)
Big Insights
Hortonworks creates its Hadoop
distribution using 100% open
source components from
Apache Foundation
Cloudera creates its Hadoop
distribution using its proprietary
components, and components
from Apache Foundation
IBM and Microsoft utilizes HDP
to power their Hadoop offerings

19.
(c) 2018 kagesenshi.org Page 22 / 24
Red Hat
Sponsored Communities
(Community)
Red Hat
(Company)
JBOSS Community
(Community)
Case Study: Several Other Red Hat Products
WildFly
Red Hat Decision
Manager
Teiid
jBPM
Drools
JBOSS Data
Virtualization
JBOSS Application
Server
Red Hat FUSE
Apicurio
Hawtio
Syndesis
Apache Foundation
(Community)
CXF
Camel
Karaf
Alongside their
enterprise product
which are derived
from upstream Open
Source communities,
Red Hat also creates
their own software
which they release
as Open Source and
create an upstream
community for it
Fedora Project
(Community)
Fedora 389
Alongside Fedora Linux, the
Fedora community also works
on emerging technologies and
one of it was the Fedora 389
Directory Server
Red Hat Identity
Manager

20.
(c) 2018 kagesenshi.org Page 23 / 24
Apple
(Company)
FreeBSD
(Community)
Case Study:AppleMac OSX
FreeBSD
Ports
MacPorts
OSX
OpenDarwin
(Community)
OpenDarwin Kernel
Other Communities
(Community)
Hundreds of Open
Source Software
Apple OSX is actually a loose
derivative of FreeBSD, with
many Apple's own proprietary
softwares and graphical
interface in it

21.
(c) 2018 kagesenshi.org Page 24 / 24
Case Study:MySQL, MariaDB &PERCONA
MySQL AB
(Company)
MySQL
Sun Microsystem
(Company)
MySQL
Oracle
(Company)
MySQL
MariaDB Foundation
(Community)
MariaDB
MariaDB AB
(Company)
MariaDB Enterprise
Percona
(Company)
Persona Server For
MySQL
MySQL Enterprise
MySQL Enterprise MySQL Enterprise
Sun acquires
MySQL AB
Oracle acquires Sun
MariaDB forked
out of MySQL
when Oracle
acquired Sun
by the founders
of MySQL AB
Percona is a company that
have been providing MySQL
support and professional
services since the days of
MySQL AB. Persona Server
provides open source
management tools for MySQL
MySQL AB controlled the
community development of
MySQL, and also provides
MySQL Enterprise with
proprietary management tools
MariaDB, while originally based off MySQL,
have diverged far from MySQL where it now
mainly focus in providing database for cloud
based database deployments. The 2
databases are no longer guarantees
compatible with each other
MariaDB AB
provides MariaDB
enterprise support
and proprietary
management tools
for MariaDB

22.
(c) 2018 kagesenshi.org Page 25 / 24
DoI HaveToUseEnterprise Product?
Are you going to use it professionally
or as hobbyist?
Are you using it for R&D or for production?
Do you have any regulations or policies against
using software without warranty or
internal expertise in production?
Do you need stable (rarely changes) base software
with enterprise grade support from external experts?
Do you have the budget to pay for the external
services?
Professionally
Production
No
Yes
Recommended
Required
Yes
Not necessary
No
No
Production
Research & Development
Yes
* Of course, standard disclaimer applies: You get what you pay for. The software as-is, without
support nor warranty, and you have to self support and handle your own warranty

23.
(c) 2018 kagesenshi.org Page 26 / 24
BeyondFree& Open SourceSoftware
●
FOSS culture triggers major change in modern human
innovation culture
– Free culture movement
– Open knowledge movement
– Creative commons
– Open Data
– Open API
– Open Hardware
– Open design movement
– Pirate Party
– .. and many others
●
Companies are also tapping into crowdsourcing and
community building for innovating their products through Open
Sourcing them or providing Open API.
– Raspberry Pi, OLPC, Kano computer kit, etc
●
The culture of sharing and collaborative content creation and
innovation is here to stay

24.
Thank You