Lua License |
|
|
From Lua 5.0, Lua is licensed under the MIT License[1]. Main reasons to switch to a standard license: 1. clear all doubts whether Lua can be used with GPL software 2. how to give credit in binaries The reasons to choose MIT is for its simplicity: The MIT license is the simplest license that we can pretend to understand, being neither lawyers nor native English speakers. The MIT license does seem to cater for all our needs, in that it covers the software and its documentation, it explicitly mentions authors and copyright owners, and demands simply that credit be given by including a copyright notice. It does not say how this is to be done, nor whether it suffices to include the copyright notice in the documentation. We are satisfied if the copyright notice is included only in the documentation, as we have tried to say in the text that precedes the license itself. -- Announcement email[2] Before Lua 5.0, Lua used its own license, which was very close to the zlib license and others, but not quite the same. Nevertheless, if you wish to use those old versions, you may hereby assume that they have all been re-licensed under the MIT license as described above. The old license is copied below for historical interests: |
|
VersionNotice: This page pertains to Lua 4 and older versions of Lua. Lua 5.0/5.1 instead use the MIT license [1]. The license change announcement can be viewed at LuaList:2002-05/msg00059.html. |
|
Currently this page is a critique of the Lua license. |
|
Here is the text (or see [original]): |
|
The main difference to Zlib License is Zlib does not require inculding copyright notice and license if Zlib is distributed in binary. There was some concerns on Lua's old license: |
|
This license seems similar to the BSD license [1]. |
|
The open source and free software communities need software with well-known licenses so that when the inevitable questions arise like "can I use Lua in my GPL'd software?" one need only consult readily available information about license compatibility [1]. |
|
While such a proprietary license is convenient for Tecgraf and PUC-Rio lawyers, it is not convenient for the free software community. The open source and free software communities need software with well-known licenses so that when the inevitable questions arise like "can I use Lua in my GPL'd software?" one need only consult readily available information about license compatibility [1]. |
Currently this page is a critique of the Lua license.
Here is the text (or see [original]):
This license seems similar to the BSD license [2].
While such a proprietary license is convenient for Tecgraf and PUC-Rio lawyers, it is not convenient for the free software community. The open source and free software communities need software with well-known licenses so that when the inevitable questions arise like "can I use Lua in my GPL'd software?" one need only consult readily available information about license compatibility [3].
The statements "... this implementation have been entirely designed and written by...", and "this implementation contains no third-party code," which supposedly must be included in the license of all derived works, is also a problem. Derived works obviously may include code not written by the Lua authors, or third-party code, causing these statements to be false.
Note: the copyright date should be updated :-) The "This implementation contains no third-party code." note is also annoying because it can means that Lua cannot include code submitted by other contributors. At least, not by without a full rewritting by the authors... Indeed, the two lines about the implementation should be removable or we should be able to edit them as "The original implementation...". --PhilippeLhoste
From Roberto's posting it seems that by "Lua implementation" they mean Lua itself and not the source code. Certainly "implementation" was a bad choice of words.