|Publisher||Massachusetts Institute of Technology|
|Linking from code with a different license||Yes|
The MIT License is a permissive free software license originating at the Massachusetts Institute of Technology (MIT). As a permissive license, it puts only very limited restriction on reuse and has therefore an excellent license compatibility. The MIT license permits reuse within proprietary software provided that all copies of the licensed software include a copy of the MIT License terms and the copyright notice. The MIT license is also compatible with many copyleft licenses, such as the GNU General Public License (GPL); MIT licensed software can be integrated into GPL software, but not the other way around.
As of 2015[update], it is the most popular software license, ahead of any GPL variant and other Free and open-source software (FOSS) licenses.[better source needed][better source needed][not in citation given] Notable projects that use one of the versions of the MIT License include Ruby on Rails, Node.js, jQuery, and the X Window System.
A common form of the MIT License (from the OSI's website, which is the same version as the "Expat License", and which is not identical to the license used in the X source code) is defined as follows:
Copyright (c) <year> <copyright holders> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copyright (C) <date> X Consortium Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of the X Consortium shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the X Consortium. X Window System is a trademark of X Consortium, Inc.
Because MIT has used many licenses for software, the Free Software Foundation considers "MIT License" ambiguous. "MIT License" may refer to the "Expat License" (used for Expat) or to the "X11 License" (also called "MIT/X Consortium License"; used for the X Window System by the MIT X Consortium). The "MIT License" published by the Open Source Initiative is the same as the "Expat License".
Except as contained in this notice, the name(s) of the above copyright holders shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization.
Comparison to other licenses
The original BSD license also includes a clause requiring all advertising of the software to display a notice crediting its authors. This "advertising clause" (since disavowed by UC Berkeley) is present in the modified MIT License used by XFree86.
Like the BSD license the MIT license does not include an express patent license. Both the BSD and the MIT licenses were drafted before the patentability of software was generally recognized under US law. A similarly permissive license, which includes an explicit contributor's patent license, is the Apache license version 2.0+.
The MIT license contains terms that are used in defining the rights of a patent holder in 35 U.S Code section 154 namely "use", and "sell". This has been construed by some commentators 35 U.S. Code section 154 defines the right of a patent holder as follow: "Every patent shall contain a short title of the invention and a grant to the patentee, his heirs or assigns, of the right to exclude others from making, using, offering for sale, or selling the invention throughout the United States or importing the invention into the United States..." The nature of the right conferred by a U.S. patent is not obvious at first, because it is a negative right, the key is in the words "right to exclude".
The University of Illinois/NCSA Open Source License combines text from both the MIT and BSD licenses; the license grant and disclaimer are taken from the MIT License.
As of 2015[update], according to Black Duck Software[better source needed] and GitHub,[better source needed] the MIT license was the most popular free software license, with the GNU GPLv2 coming second. In June 2016 an analysis of the Fedora Project's packages revealed the MIT as most used license.[not in citation given]
- Software using the MIT license
- Comparison of free and open-source software licenses
- ISC license – similar to the MIT license, but with language deemed unnecessary removed
- Lawrence Rosen, OPEN SOURCE LICENSING, p.85 (Prentice Hall PTR, 1st ed. 2004)
- Hanwell, Marcus D. (2014-01-28). "Should I use a permissive license? Copyleft? Or something in the middle?". opensource.com. Retrieved 2015-05-30.
Permissive licensing simplifies things One reason the business world, and more and more developers [...], favor permissive licenses is in the simplicity of reuse. The license usually only pertains to the source code that is licensed and makes no attempt to infer any conditions upon any other component, and because of this there is no need to define what constitutes a derived work. I have also never seen a license compatibility chart for permissive licenses; it seems that they are all compatible.
- "Licence Compatibility and Interoperability". Open-Source Software - Develop, share, and reuse open source software for public administrations. joinup.ec.europa.eu. Retrieved 2015-05-30.
The licences for distributing free or open source software (FOSS) are divided in two families: permissive and copyleft. Permissive licences (BSD, MIT, X11, Apache, Zope) are generally compatible and interoperable with most other licences, tolerating to merge, combine or improve the covered code and to re-distribute it under many licences (including non-free or 'proprietary').
- "Various Licenses and Comments about Them". Free Software Foundation. Retrieved 17 July 2013.
- "Top 20 licenses". Black Duck Software. 19 November 2015. Retrieved 19 November 2015.
1. MIT license 24%, 2. GNU General Public License (GPL) 2.0 23%
- Balter, Ben (2015-03-09). "Open source license usage on GitHub.com". github.com. Retrieved 2015-11-21.
1 MIT 44.69%, 2 Other 15.68%
- Anwesha Das (22 June 2016). "Software Licenses in Fedora Ecosystem". anweshadas.in. Retrieved 2016-06-27.
In the above bar-chart I have counted GPL and its different versions as one family, and I did the same with LGPL too. From this diagram it is very much clear that the MIT License is the most used license, with a total number of use case of 2706.Therefore comes GPL(i.e GNU General Public License) and its different versions, BSD, LGPL(i.e GNU Lesser General Public License) and its different versions, ASL (i.e Apache Software License) family, MPL (i.e Mozilla Public License). Apart from these licenses there are projects who has submitted themselves in to Public Domain and that number is 137.(Retracted, see https://anweshadas.in/software-licenses-in-fedora-ecosystem/)
- "Open Source Initiative OSI – The MIT License:Licensing". Open Source Initiative. Retrieved 5 December 2010.
- "3.3. X Consortium", 3. X/MIT Licenses, The XFree86 Project, March 2004
- "Various Licenses and Comments about Them#Expat License". Free Software Foundation. Retrieved 5 December 2010.
- "Various Licenses and Comments about Them#X11 License". Free Software Foundation. Retrieved 5 December 2010.
- Dickey, Thomas E. "NCURSES — Frequently Asked Questions (FAQ)".
- "To All Licensees, Distributors of Any Version of BSD". University of California, Berkeley. 1999-07-22. Retrieved 2006-11-15.
- Stern and Allen, Open Source Licensing, p. 495 in Understanding the Intellectual Property License 2013 (Practicing Law Institute 2013)
- Christian H. Nadan, Closing the Loophole; Open Source Licensing and the Implied Patent License, THE COMPUTER AND INTERNET LAWYER, Vol. 26, No. 8 (Aug. 2009) available at http://www.scribd.com/doc/46088081/Closing-the-Loophole-Open-Source-Licensing-and-the-Implied-Patent-License-Nadan who argues that "By using patent terms like "deal in", "use", and "sell", the MIT license grant is more likely to be deemed to include express patent rights than the BSD license.
- 35 U.S. Code section 154 at http://www.law.cornell.edu/uscode/text/35/154; Stern and Allen, supra, p. 495
- Bitlaw, 1996-2013 Daniel A. Tysver (Beck & Tysver) http://www.bitlaw.com/patent/rights.html
- "Copyright Policy". OpenBSD. Retrieved 6 June 2016.
The ISC copyright is functionally equivalent to a two-term BSD copyright with language removed that is made unnecessary by the Berne convention.
- de Raadt, Theo (21 March 2008). "Re: BSD Documentation License?". openbsd-misc (Mailing list).
- Mitchell, Kyle E. (2016-09-21). "The MIT License, Line by Line". /dev/lawyer. Archived from the original on 2016-09-28. Retrieved 2016-09-28.