Open Source Licenses and Tools
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


Open Source Licenses and Tools

Uploaded on


Comparative brief on most commonly used and popular open source

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. G2iX Background Founded 2001 Focused on enabling businesses with innovative solutions Award-winning engineering team Globally Delivered Engineering Services World-class open source engineering automation Leading open source applications Scalable cloud computing platform Build and Test Automation Our employees from Australia to Germany, from US to the Philippines consistently deliver innovation for our worldwide customers Cloud Computing Infrastructure 2
  • 2. Open Source Licenses 3
  • 3. Open Source Licenses Freedom to copy Freedom to create derivative work Freedom to distribute derivative work Licenses must be distributed with the software Licenses have a warranty disclaimer
  • 4. Open Source Licenses GNU General Public License (GPL) strong copyleft license requires distribution to remain under GPL terms requires source code to be distributed together with the binary cannot be used in a proprietary software Linux, MySQL, Mozilla Suite, Alfresco
  • 5. Open Source Licenses MIT License simplest, non restrictive PuTTy, RoR, Liferay, EasyMock Modified BSD Licenses no contributor endorsement can be used in a proprietary software PostgreSQL, Debian
  • 6. Open Source Licenses Apache License 2.0 provides more protection to Open Source developer no endorsement redistribute in “Object or Source” form LICENSE and NOTICE Ant, Maven, Struts, Tomcat
  • 7. Open Source Licenses “Lesser” General Public License (LGPL) compromise between GPL and BSD/MIT licenses primarily used for software libraries can be used by non-(L)GPLed program Mozilla Suite, OpenOffice
  • 8. Open Source Licenses Eclipse Public License (EPL) source code not required allow different license for portions added or enhanced business friendly Websphere, Weblogic, Oracle
  • 9. Open Source Licenses Mozilla Public License (MPL) hybrid of modified BSD license and GPL code copied or changed under MPL must stay under MPL terms can be combined with other licenses Mozilla Suite App, Mozilla Thunderbird
  • 10. License Compatibility a license x is compatible with license y if work licensed under x can be distributed under y terms GPL compatible licenses
  • 11. Dual Licenses simultaneous licensing of software under both open- source and proprietary licenses motivations for dual licensing ensure license compatibility make money recipients can choose which terms to use or distribute the software under MySQL, Ruby, Perl, Mozilla
  • 12. MIT BSD ASF MPL EPL GPL LGPL Disclaimer of Liability Yes Yes Yes Yes Yes Yes Yes Preserve Copyright Yes Yes Yes Yes Yes Yes Yes Notice Sold for a profit Yes Yes Yes Yes Yes Yes Yes Use in Commercial Closed Source Yes Yes Yes Yes Yes No Depends Software Use in endorsement Yes No No Yes Yes Yes Yes 13
  • 13. MIT BSD ASF MPL EPL GPL LGPL Release changes under a different Yes Yes Yes No No No No license Distribute binary Yes Yes Yes Limit Yes No No without source code Link from code w/ a Yes Yes Yes Yes Yes No Yes different license Copyleft No No No Yes Yes Yes Yes Yes GPL compatible Yes Yes No No Yes Yes GPL3 14
  • 14. How Many Open Source Licenses Do You Need? 15
  • 15. How Many Open Source Licenses Do You Need? A “gift” license usable in open source or proprietary software Apache License 2.0 A “gift” license A “sharing with rules” license copyleft license GPL 3 An “in-between” license “sharing with rules” but usable in proprietary software LGPL 3
  • 16. Open Source Software 17
  • 17. Benefits of Open Source Software low or no cost faster development process reliability and quality of code flexibility
  • 18. Open Source Derived Solution Distributed Engineering with a common build mapping Asynchronous Extensive re-use Development of software around the artifacts world (Ingredients) Frequent testing of integration and functions Adapting the best practices of Open Source development processes to the Enterprise 19
  • 19. Maestro Build Automation Maven Features Declarative model for software builds Modules for: Compiling / Assembly and Distribution / Tests / Reporting Plug In Architecture Over 100 plug ins for multiple life cycle Integration to IDEs Rich reporting features Policy Enforcement Enables: Repeatable build processes Standardization Higher visibility of progress 20
  • 20. Maestro Repository Manager Archiva Features Provides a common, high volume repository for artifacts/ “ingredients” Accessibility from multiple build systems Access control Versioning of artifacts Support for Remote Proxying Support for Virtual Repositories Role Based Security WebDAV and WS Integration Graphical Administration Policy Management Search Engine RSS Feeds and Reports Enables: Build consistency Higher re-use of components Predictability of assembly Unified source for developer tools 21
  • 21. Maestro Continuous Integration Continuum Features Automates the “build process” Tight integration with Maven Automatic triggering of builds Reports for build success / failures and charts over time Deployment to multiple configurations Automated Release Management Distributed builds Parallel Builds Templating Multiple SCM Support Remote Access Enables Daily compilation of code from distributed or Asynchronous teams Automatic deployment to multiple configurations Automatic triggers for acceptance criteria Full life cycle reporting 22
  • 22. Resources How-Many-Open-Source-Licenses-Do-You-Need.htm 23
  • 23. Thank you!