Your SlideShare is downloading. ×
Open Source vs Proprietary
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Open Source vs Proprietary

365
views

Published on

Set of slides prepared for a debate on the topic for Imperial Institute of Higher Education.

Set of slides prepared for a debate on the topic for Imperial Institute of Higher Education.


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
365
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Debate conducted at Imperial Institute of Higher Education
  • 2. "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
  • 3. Game Plan – Round 1 What’s Open Source? How to Open Source? Open Source squashes Proprietary
  • 4. What’s Open Source? –opensource.orgNOT 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
  • 5. 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?
  • 6. Battle of ChoicesCriteria Public BSD/ ASLv2 GPL LGPL MPL/ CPL/ Domain MIT (Apache) (v2) CDDL EPLCode is protected by No Yes Yes Yes Yes Yes Yescopyright?Code can be used in Yes Yes Yes No Yes Yes Yesclosed source projects?Program that Yes Yes Yes No Yes Yes Yesuses (incorporates) thesoftware can be soldcommercially?Source to bug fixes and No No No Yes Yes Yes Yesmodifications must bereleased?Provides explicit patent No No Yes No No Yes Yeslicense?
  • 7. The HitsOpen Source ProprietaryCustomizability/Modifiability -> Better Limited FlexibilityFitLow Cost High CostTight security Comparatively Less SecureMore Innovation Limited to the innovation of the few internal developers
  • 8. Continuing to Strike – Open Source Adaption of New Trends Faster Promotion of Re-Distribution
  • 9. 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
  • 10. ReferencesImages http://www.slideshare.net/secret/2rFjfZ80QDK3zh
  • 11. Why Open Source?
  • 12. When users dont control the program, the program controlsthe users.The developer controls the program, and through it controls theusers.This non-free or “proprietary” program is therefore aninstrument of unjust power.
  • 13. Game Plan – Round 3 Current Track Record Future of Open Source
  • 14. 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
  • 15. 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
  • 16. 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
  • 17. 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”
  • 18. 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

×