Lisensi MIT

Lisensi MIT
Penerbit	Massachusetts Institute of Technology
Kompatibel dengan DFSG	Ya
Perangkat lunak bebas	Ya
Disetujui OSI	Ya
Kompatibel dengan GPL	Ya
Copyleft	Tidak
Penautan dari kode program dengan lisensi berbeda	Ya

Lisensi MIT adalah lisensi perangkat lunak bebas permisif yang berasal dari Massachusetts Institute of Technology (MIT).^[5] Sebagai lisensi permisif, Lisensi MIT memberikan batasan yang sangat longgar tentang penggunaan kembali dan memiliki kompatibilitas lisensi yang sangat baik.^[6]^[7] Lisensi MIT mengizinkan penggunaan kembali perangkat lunak dengan lisensi MIT menjadi perangkat lunak berpemilik asalkan menyediakan salinan semua persyaratan dan pemberitahuan hak cipta dari Lisensi MIT. Lisensi MIT juga kompatibel dengan banyak lisensi copyleft, misalnya Lisensi Publik Umum GNU (GPL); Perangkat lunak berlisensi MIT dapat diintegrasikan ke dalam perangkat lunak GPL, tetapi tidak sebaliknya.^[8]

Ketentuan lisensi

Bentuk umum Lisensi MIT (dari situs web OSI, yang merupakan versi yang sama dengan "Lisensi Expat") didefinisikan sebagai berikut:

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.

Referensi

^
"License information". The Debian Project. Software in the Public Interest (dipublikasikan tanggal 2017-07-12). 1997–2017. Diarsipkan dari versi asli tanggal 2017-07-20. Diakses tanggal 2017-07-20.
... 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
...
^ ^a ^b ^c "Various Licenses and Comments about Them". The GNU Project. Free Software Foundation (dipublikasikan tanggal 2017-04-04). 2014–2017. Expat License. Diarsipkan dari versi asli tanggal 2017-07-20. Diakses tanggal 2017-07-20. ... 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. ...
^ ^a ^b ^c "Various Licenses and Comments about Them". The GNU Project. Free Software Foundation (dipublikasikan tanggal 2017-04-04). 2014–2017. X11 License. Diarsipkan dari versi asli tanggal 2017-07-20. Diakses tanggal 2017-07-20. ... 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. ...
^
"Licenses by Name". Open Source Initiative. n.d. Diarsipkan dari versi asli tanggal 2017-07-20. Diakses tanggal 2017-07-20.
... The following licenses have been approved by the OSI. ...
...
MIT License (MIT)
...
^ 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. Diakses tanggal 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. Diarsipkan dari versi asli tanggal 2015-06-17. Diakses tanggal 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. Diakses tanggal 17 July 2013.