Systematize Comment License For Free

Overview of the process Submit the license to license-review mailing list. ... Join the mailing list and follow the reviews. ... Reacting to comments, issuing new license versions. ... Reaching consensus for a decision. ... Issuing the final decision. ... Request for approval of a legacy license. ... Request for approval of a new license.

Limitations of the MIT License No warranty: The MIT License disclaims any warranties, meaning the software is provided "as is". The creators or copyright holders do not make any guarantees regarding the software's functionality, reliability, or suitability for a particular purpose.

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

The MIT license is permissive, placing very few restrictions on how the software can be used, while the GPL license is restrictive, requiring that any changes made to the code be released under the same license, and any software that uses the code must also be released under the same license.

No, you can't change (unless you're the author) code that's been released under GPL and turn it into another license including MIT. Section 2 says that modified versions you distribute must be licensed to all third parties under the GPL.

The MIT License is highly compatible with other permissive licenses. Including the BSD family of licenses. It is generally compatible with GNU GPL group of licenses. However if you distribute the code that contains or is derivative of GNU GPL code the final project must of GPL compliant.

Like the Apache 2.0, and BSD family of licenses the MIT License is a permissive software license that places few restrictions of reuse. Users of software using an MIT License are permitted to use, copy, modify, merge publish, distribute, sublicense and sell copies of the software.