KEMBAR78
Open Source vs Proprietary | PPTX
Debate conducted at Imperial Institute of Higher
                                      Education
"To be able to choose between proprietary software
      packages is to be able to choose your master.
  Freedom means not having a master. And in
  the area of computing, freedom means not using
                             proprietary software."

                                -Richard M. Stallman
Game Plan – Round 1
 What’s Open Source?


 How to Open Source?


 Open Source squashes Proprietary
What’s Open Source? –
opensource.org
NOT ONLY access to the source code… but also,
 Free Redistribution
 Source Code
 Derived Works
 Integrity of the Author’s Source Code
 No Discrimination Against Persons or Groups
 No Discrimination Against Fields of Endeavor
 Distribution of License
 License Must Not Be Specific to a Product
 License Must Not Restrict Other Software
 License Must Be Technology-Neutral
Licensing
 Open Source SW – SW distributed under the license
  which follows the Open Source definition

 How to choose a license?
 Do you wish to give control of your code to others?
 Do you want to allow people to use your code in non open-source
  programs?
 If somebody uses your code in their program and sells their program for
  money, do you want some of that money?
 If somebody uses and distributes your code and improves it (fixes bugs
  or adds features) do you want to make them give you the improvements
  back so you can use them too?
Battle of Choices
Criteria                   Public BSD/ ASLv2     GPL    LGPL MPL/   CPL/
                           Domain MIT (Apache)   (v2)        CDDL   EPL


Code is protected by       No     Yes   Yes      Yes    Yes   Yes   Yes
copyright?
Code can be used in        Yes    Yes   Yes      No     Yes   Yes   Yes
closed source projects?
Program that               Yes    Yes   Yes      No     Yes   Yes   Yes
uses (incorporates) the
software can be sold
commercially?

Source to bug fixes and    No     No    No       Yes    Yes   Yes   Yes
modifications must be
released?
Provides explicit patent   No     No    Yes      No     No    Yes   Yes
license?
The Hits
Open Source                             Proprietary

Customizability/Modifiability -> Better Limited Flexibility
Fit
Low Cost                                High Cost

Tight security                          Comparatively Less Secure

More Innovation                         Limited to the innovation of the few
                                        internal developers
Continuing to Strike – Open Source
 Adaption of New Trends Faster


 Promotion of Re-Distribution
References
 http://www.opensource.org
 http://blog.marycamacho.com/2011/11/decision-tree-
  for-determining.html
 http://www.zdnet.com/blog/burnette/how-to-pick-
  an-open-source-license-part-2/131?tag=content;siu-
  container
References
Images
 http://www.slideshare.net/secret/2rFjfZ80QDK3zh
Why Open Source?
When users don't control the program, the program controls
the users.

The developer controls the program, and through it controls the
users.

This non-free or “proprietary” program is therefore an
instrument of unjust power.
Game Plan – Round 3
 Current Track Record


 Future of Open Source
Government Arena
 In December 2000, the NSA publicly announced the
 development and release of Security-Enhanced Linux
 “we recognized that open-source had tremendous
 potential within government technology systems.”
                               ~ National Security Agency (NSA) of USA


 “Too many government IT projects have failed because
 they started without testing whether the end product
 was feasible”.
~ Mark O’Neill, head of innovation and delivery in the Government Digital
                                                        Service (GDS), UK
Microsoft going Open Source
 Open Sourcing ASP.NET MVC4.0, WebAPI and Razor View Engine


 Becoming A Top-20 Contributor To The Linux Kernel


 Supporting open-source platforms in Azure


 Supporting Apache, PHP and Ruby on Windows


 Making Windows a great platform for open-source


 Wheel-Reinventing Reduced
    Including JQuery and Modernizr in ASP.NET MVC 3.0
Survey –             30th     May 2012
 740 questioned
    59% non vendors
    41% OSS vendors
 62% use OSS and platforms
 1/3rd – More than 75% OSS deployments


 Adoption rate of OSS in non-technical arenas increased by 42%
 Enterprise – 40%
 Automotive Industry – 59% deployments


 More than 50% SW acquired in the next 5 years will be Open Source
Reasons for the Choice
 Free from vendor lock-ins


 Low Cost


 Better Quality
“The quality of open source, and the ability to continuously improve, is
  now one of the top reasons for its adoption”
References
 http://www.zdnet.com/blog/open-source/open-source-
    and-the-national-security-agency-together-again/11079
   http://www.techrepublic.com/blog/european-
    technology/how-open-source-software-can-head-off-it-
    disasters/705
   http://www.zdnet.com/blog/open-source/open-source-
    driving-cloud-big-data-mobile-survey-finds/11015
   http://www.zdnet.com/blog/microsoft/microsoft-is-
    serious-about-open-source-10-proof-points/12784
   http://www.slideshare.net/secret/2rFjfZ80QDK3zh
Open Source vs Proprietary

Open Source vs Proprietary

  • 1.
    Debate conducted atImperial Institute of Higher Education
  • 2.
    "To be ableto choose between proprietary software packages is to be able to choose your master. Freedom means not having a master. And in the area of computing, freedom means not using proprietary software." -Richard M. Stallman
  • 3.
    Game Plan –Round 1  What’s Open Source?  How to Open Source?  Open Source squashes Proprietary
  • 5.
    What’s Open Source?– opensource.org NOT ONLY access to the source code… but also,  Free Redistribution  Source Code  Derived Works  Integrity of the Author’s Source Code  No Discrimination Against Persons or Groups  No Discrimination Against Fields of Endeavor  Distribution of License  License Must Not Be Specific to a Product  License Must Not Restrict Other Software  License Must Be Technology-Neutral
  • 7.
    Licensing  Open SourceSW – SW distributed under the license which follows the Open Source definition  How to choose a license?  Do you wish to give control of your code to others?  Do you want to allow people to use your code in non open-source programs?  If somebody uses your code in their program and sells their program for money, do you want some of that money?  If somebody uses and distributes your code and improves it (fixes bugs or adds features) do you want to make them give you the improvements back so you can use them too?
  • 9.
    Battle of Choices Criteria Public BSD/ ASLv2 GPL LGPL MPL/ CPL/ Domain MIT (Apache) (v2) CDDL EPL Code is protected by No Yes Yes Yes Yes Yes Yes copyright? Code can be used in Yes Yes Yes No Yes Yes Yes closed source projects? Program that Yes Yes Yes No Yes Yes Yes uses (incorporates) the software can be sold commercially? Source to bug fixes and No No No Yes Yes Yes Yes modifications must be released? Provides explicit patent No No Yes No No Yes Yes license?
  • 11.
    The Hits Open Source Proprietary Customizability/Modifiability -> Better Limited Flexibility Fit Low Cost High Cost Tight security Comparatively Less Secure More Innovation Limited to the innovation of the few internal developers
  • 14.
    Continuing to Strike– Open Source  Adaption of New Trends Faster  Promotion of Re-Distribution
  • 15.
    References  http://www.opensource.org  http://blog.marycamacho.com/2011/11/decision-tree- for-determining.html  http://www.zdnet.com/blog/burnette/how-to-pick- an-open-source-license-part-2/131?tag=content;siu- container
  • 16.
  • 17.
  • 18.
    When users don'tcontrol the program, the program controls the users. The developer controls the program, and through it controls the users. This non-free or “proprietary” program is therefore an instrument of unjust power.
  • 19.
    Game Plan –Round 3  Current Track Record  Future of Open Source
  • 21.
    Government Arena  InDecember 2000, the NSA publicly announced the development and release of Security-Enhanced Linux “we recognized that open-source had tremendous potential within government technology systems.” ~ National Security Agency (NSA) of USA  “Too many government IT projects have failed because they started without testing whether the end product was feasible”. ~ Mark O’Neill, head of innovation and delivery in the Government Digital Service (GDS), UK
  • 22.
    Microsoft going OpenSource  Open Sourcing ASP.NET MVC4.0, WebAPI and Razor View Engine  Becoming A Top-20 Contributor To The Linux Kernel  Supporting open-source platforms in Azure  Supporting Apache, PHP and Ruby on Windows  Making Windows a great platform for open-source  Wheel-Reinventing Reduced  Including JQuery and Modernizr in ASP.NET MVC 3.0
  • 24.
    Survey – 30th May 2012  740 questioned  59% non vendors  41% OSS vendors  62% use OSS and platforms  1/3rd – More than 75% OSS deployments  Adoption rate of OSS in non-technical arenas increased by 42%  Enterprise – 40%  Automotive Industry – 59% deployments  More than 50% SW acquired in the next 5 years will be Open Source
  • 27.
    Reasons for theChoice  Free from vendor lock-ins  Low Cost  Better Quality “The quality of open source, and the ability to continuously improve, is now one of the top reasons for its adoption”
  • 28.
    References  http://www.zdnet.com/blog/open-source/open-source- and-the-national-security-agency-together-again/11079  http://www.techrepublic.com/blog/european- technology/how-open-source-software-can-head-off-it- disasters/705  http://www.zdnet.com/blog/open-source/open-source- driving-cloud-big-data-mobile-survey-finds/11015  http://www.zdnet.com/blog/microsoft/microsoft-is- serious-about-open-source-10-proof-points/12784  http://www.slideshare.net/secret/2rFjfZ80QDK3zh