MIT License

Print Print
Reading time 13:16

MIT License
MIT logo.svg
PublisherMassachusetts Institute of Technology
SPDX identifierMIT
Debian FSG compatibleYes[1]
FSF approvedYes[2][3]
OSI approvedYes[4]
GPL compatibleYes[2][3]
CopyleftNo[2][3]
Linking from code with a different licenceYes

The MIT License (X11 License)[6] is a permissive free software license originating at the Massachusetts Institute of Technology (MIT)[7] in the late 1980s.[8] As a permissive license, it puts only very limited restriction on reuse and has, therefore, high license compatibility.[9][10] The Wikipedia and Wikimedia Commons projects use the alternative name Expat License.

The MIT license is compatible with many copyleft licenses, such as the GNU General Public License (GPL); MIT licensed software can be re-licensed as GPL software, and integrated with other GPL software, but not the other way around.[11] The MIT license also permits reuse within proprietary software, provided that either all copies of the licensed software include a copy of the MIT License terms and the copyright notice, or the software is re-licensed to remove this requirement. MIT-licensed software can also be re-licensed as proprietary software,[12][10] which distinguishes it from copyleft software licenses. As of 2020, MIT was the most popular software license found in one analysis,[13] continuing from reports in 2015 that MIT was the most popular software license on GitHub, ahead of any GPL variant and other free and open-source software (FOSS) licenses.[14]

Notable projects that use the MIT License include the X Window System, Ruby on Rails, Nim, Node.js, Lua and jQuery. Notable companies using the MIT License include Microsoft (.NET Core), Google (Angular) and Facebook (React).

License terms

The most common form of the MIT License wording is the following,[citation needed] which is identical to the list of licenses[15] maintained by the Open Source Initiative's website and also known as the "Expat License": 

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.

An intermediate form of license used by the X Consortium for X11 used the following wording:[16]

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.

Minor ambiguity and variants

MIT has been using many licenses for software since its creation, so the phrase "the MIT License" is theoretically ambiguous.[17] For example, MIT offers four licensing options for the FFTW[18] C source code library, one of which is the GPLv 2.0 and the other three of which are not open-source.

"MIT License" may refer to the Expat License (used for the XML parsing library Expat)[19] or to the X11 License (also called "MIT/X Consortium License"; used for X Window System by the MIT X Consortium).[20] The "MIT License" published by the Open Source Initiative[15] is the same as the "Expat License".

The X Consortium was dissolved late in 1996, and its assets transferred to The Open Group,[21] which released X11R6 initially under the same license. The X11 License[20] and the X11R6 "MIT License" chosen for ncurses by the Free Software Foundation[22] both include the following clause, absent in the Expat License:[19]

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.

As of 2020, the successor to the X Window System is the X.Org Server, which is licensed under what is effectively the common MIT license, according to the X.org licensing page:

The X.Org Foundation has chosen the following format of the MIT License as the preferred format for code included in the X Window System distribution. This is a slight variant of the common MIT license form published by the Open Source Initiative

The "slight variant" is the addition of the phrase "(including the next paragraph)".

Some ignore this history, referring to only one MIT license, as illustrated by GitHub's licensing advice and the legal text for the MIT License at GitHub's service choosealicense.com.

Comparison to other licenses

BSD

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[23]) is present in the modified MIT License used by XFree86.

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.

The ISC license contains similarities to both the MIT and simplified BSD licenses, the biggest difference being that language deemed unnecessary by the Berne Convention is omitted.[24][25]

GNU GPL

The GNU GPL is explicit about the patent grant an author would be giving when the code (or derivative work) is distributed,[26] the MIT license does not discuss patents. Moreover, the GPL license impacts "derivative works", but the MIT license does not.

Relation to patents

Like the BSD license, the MIT license does not include an express patent license although some commentators[27][28] state that the grant of rights covers all potential restrictions including patents. Both the BSD and the MIT licenses were drafted before the patentability of software was generally recognized under US law.[29] The Apache License version 2.0[2] is a similarly permissive license that includes an explicit contributor's patent license. Of specific relevance to US jurisdictions, the MIT license uses the terms "sell" and "use" that are also used in defining the rights of a patent holder in Title 35 of the United States Code section 154. This has been construed by some commentators[30][31] as an unconventional but implicit license in the US to use any underlying patents.

Origins

One of the originators of the MIT license, computer scientist Jerry Saltzer, has published his recollections of its early development, along with documentary evidence.[32] See also.[8]

Reception

As of 2020, according to WhiteSource Software[13] the MIT license was used in 27% of four million open source packages. As of 2015, according to Black Duck Software[33][better source needed] and a 2015 blog[14] from GitHub, the MIT license was the most popular free software license, with the GNU GPLv2 coming second in their sample of repositories.

See also

  • Comparison of free and open-source software licenses
  • ISC license – similar to the MIT license, but with language deemed unnecessary removed
  • Category:Software using the MIT license

References

  1. ^ "License information". The Debian Project. Software in the Public Interest (published July 12, 2017). 1997–2017. Archived from the original on July 20, 2017. Retrieved July 20, 2017. ... This page presents the opinion of some debian-legal contributors on how certain licenses follow the Debian Free Software Guidelines (DFSG). ... Licenses currently found in Debian main include:
    • ...
    • Expat/MIT-style licenses
    • ...
  2. ^ a b c d "Various Licenses and Comments about Them". The GNU Project. Free Software Foundation (published April 4, 2017). 2014–2017. Expat License. Archived from the original on July 20, 2017. Retrieved July 20, 2017. ... This is a lax, permissive non-copyleft free software license, compatible with the GNU GPL. It is sometimes ambiguously referred to as the MIT License. ...
  3. ^ a b c "Various Licenses and Comments about Them". The GNU Project. Free Software Foundation (published April 4, 2017). 2014–2017. X11 License. Archived from the original on July 20, 2017. Retrieved July 20, 2017. ... This is a lax permissive non-copyleft free software license, compatible with the GNU GPL. ... This license is sometimes called the MIT license, but that term is misleading, since MIT has used many licenses for software. ...
  4. ^ "Licenses by Name". Open Source Initiative. n.d. Archived from the original on July 20, 2017. Retrieved July 20, 2017. ... The following licenses have been approved by the OSI. ...
    • ...
    • MIT License (MIT)
    • ...
  5. ^ Certified Copyfree Licenses
  6. ^ "X11 License Explained in Plain English - TLDRLegal". tldrlegal.com. Retrieved March 26, 2021.
  7. ^ Lawrence Rosen, OPEN SOURCE LICENSING, p.85 (Prentice Hall PTR, 1st ed. 2004)
  8. ^ a b "The mysterious history of the MIT License". opensource.com. opensource.com. Retrieved July 30, 2019. The date? The best single answer is probably 1987. But the complete story is more complicated and even a little mysterious. [...] Precursors from 1985. The X Consortium or X11 License variant from 1987. Or the Expat License from 1998 or 1999.
  9. ^ Hanwell, Marcus D. (January 28, 2014). "Should I use a permissive license? Copyleft? Or something in the middle?". opensource.com. Retrieved May 30, 2015. 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.
  10. ^ a b "Licence Compatibility and Interoperability". Open-Source Software - Develop, share, and reuse open source software for public administrations. joinup.ec.europa.eu. Archived from the original on June 17, 2015. Retrieved May 30, 2015. 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').
  11. ^ "Various Licenses and Comments about Them". Free Software Foundation. Retrieved July 17, 2013.
  12. ^ https://softwareengineering.stackexchange.com/questions/264700/paid-software-includes-mit-licensed-library-does-that-put-my-app-under-mit-too
  13. ^ a b "Open Source Licenses in 2020: Trends and Predictions". May 3, 2020. Archived from the original on May 3, 2020. Retrieved May 3, 2020.
  14. ^ a b Balter, Ben (March 9, 2015). "Open source license usage on GitHub.com". github.com. Retrieved November 21, 2015. 1 MIT 44.69%, 2 Other 15.68%
  15. ^ a b "Open Source Initiative OSI – The MIT License:Licensing". Open Source Initiative. Retrieved December 5, 2010.
  16. ^ "3.3. X Consortium", 3. X/MIT Licenses, The XFree86 Project, March 2004
  17. ^ "Various Licenses and Comments about Them". GNU Project. Retrieved July 17, 2020.
  18. ^ "FFTW - Fastest Fourier Transform in the West". Massachusetts Institute of Technology. Retrieved July 17, 2020.
  19. ^ a b "Various Licenses and Comments about Them#Expat License". Free Software Foundation. Retrieved December 5, 2010.
  20. ^ a b "Various Licenses and Comments about Them#X11 License". Free Software Foundation. Retrieved December 5, 2010.
  21. ^ Dickey, Thomas E. "Copyrights/comments". Retrieved October 6, 2020.
  22. ^ Dickey, Thomas E. "NCURSES — Frequently Asked Questions (FAQ)".
  23. ^ "To All Licensees, Distributors of Any Version of BSD". University of California, Berkeley. July 22, 1999. Retrieved November 15, 2006.
  24. ^ "Copyright Policy". OpenBSD. Retrieved June 6, 2016. The ISC copyright is functionally equivalent to a two-term BSD copyright with language removed that is made unnecessary by the Berne convention.
  25. ^ de Raadt, Theo (March 21, 2008). "Re: BSD Documentation License?". openbsd-misc (Mailing list).
  26. ^ "Patents and GPLv3 - FSFE". FSFE - Free Software Foundation Europe. Retrieved December 1, 2020.
  27. ^ "Why so little love for the patent grant in the MIT License?". January 23, 2021. Archived from the original on January 23, 2021. Retrieved January 23, 2021.
  28. ^ "Free and open source software and your patents". May 3, 2020. Archived from the original on May 3, 2020. Retrieved May 3, 2020.
  29. ^ Stern and Allen, Open Source Licensing, p. 495 in Understanding the Intellectual Property License 2013 (Practicing Law Institute 2013)
  30. ^ "The MIT License, Line by Line". May 3, 2020. Archived from the original on May 3, 2020. Retrieved May 3, 2020.
  31. ^ 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) 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."
  32. ^ Saltzer, Jerome H (November 18, 2020). "The origin of the "MIT license"". IEEE Annals of the History of Computing. 42 (4): 94–98. doi:. ISSN 1934-1547. Retrieved November 28, 2020. open access
  33. ^ "Top 20 licenses". Black Duck Software. November 19, 2015. Archived from the original on September 4, 2013. Retrieved November 19, 2015. 1. MIT license 24%, 2. GNU General Public License (GPL) 2.0 23%

Further reading

External links

By: Wikipedia.org
Edited: 2021-06-18 15:09:41
Source: Wikipedia.org

© 2024 CodeDocs.org
 Privacy Policy • Contact Us • Terms of Use