Skip to content
Akshay Joshi edited this page Jan 27, 2016 · 43 revisions

Summarized license comparisons

MIT License

  • Permissive free software license
  • It comes under FOSS license and is also compatible with many copyleft licenses like GPL
  • Very limited restrictions on reuse
  • According to Github data, it is the most popular one
  • MIT license can be integrated into GPL
  • The MIT license specifically grants the right to "sublicense" in the text of the license itself. The right to sublicense means that the party that receives code under the MIT license grant has the legal right to grant all license rights it received downstream to a third party to whom that licensee distributes the MIT code.
  • Notable Software licenses with MIT License: Ruby on Rails, Node.js, jQuery and the X Window System Source: [MIT License wiki page] (https://en.wikipedia.org/wiki/MIT_License)
  • The right to modify and distribute it privately is right guaranteed (https://www.mozilla.org/en-US/MPL/2.0/FAQ/)

GNU GPL v3

  • Must state the changes.Run, study, share and modify software
  • Copyleft license;Free software license
  • Must disclose source
  • Must include license
  • Can be used for commercial use
  • Cannot hold liable and cannot sublicense
  • There is no warranty for this free software
  • Source

Apache License

Mozilla Public License (MPL 2.0)

Eclipse Public License (1.0)

  1. It features weaker Copyleft provisions. (https://en.wikipedia.org/wiki/Eclipse_Public_License)
  2. The EPL grants these rights:
    • to copy, adapt and distribute the program in source or object code form
    • to distribute the code in object code form alone under a different licence, provided that licence is compatible with the EPL
    • patent rights from all contributors to use and make available the code
    • to distribute works which contain the code in combination with new code modules, and to license the new code modules in any way the distributor wishes (http://oss-watch.ac.uk/resources/epl)

Public Domain "Unlicensed"

  1. The Unlicense is a template for disclaiming copyright monopoly interest in software you've written; in other words, it is a template for dedicating your software to the public domain.
  2. This is free and unencumbered software released into the public domain.
  3. Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.(http://unlicense.org)
  4. There are four common ways that works arrive in the public domain: -the copyright has expired -the copyright owner failed to follow copyright renewal rules -the copyright owner deliberately places it in the public domain, known as “dedication,” or -copyright law does not protect this type of work. (http://fairuse.stanford.edu/overview/public-domain/welcome/)
  5. It's not global :- It doesn't make sense outside of a commonwealth ecosystem, is explicitly illegal in some places (Germany), and of unclear legality in others (Australia) [source :- http://programmers.stackexchange.com/questions/147111/what-is-wrong-with-the-unlicense]
  6. As a condition to exercising the rights and licenses granted for EPL - V1.0, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program. [source:- https://www.eclipse.org/legal/epl-v10.html]

Clone this wiki locally