hello friends! new(ish)!
Licenses: Difference between revisions
Jump to navigation
Jump to search
>Bathsubeki No edit summary |
>Thunder (Added MIT License info and extra source.) |
||
| Line 5: | Line 5: | ||
*[http://www.linfo.org/bsdlicense.html BSD License] is much more permissive than the GPL. You basically can do anything you want. You can even incorporate BSD-licensed code in your closed-source proprietary software, effectively re-licensing the source code, so long as you give the original author(s) credit as appropriate. | *[http://www.linfo.org/bsdlicense.html BSD License] is much more permissive than the GPL. You basically can do anything you want. You can even incorporate BSD-licensed code in your closed-source proprietary software, effectively re-licensing the source code, so long as you give the original author(s) credit as appropriate. | ||
*[https://www.apache.org/licenses/LICENSE-2.0.html Apache License] is known for protecting users against patent suing. | *[https://www.apache.org/licenses/LICENSE-2.0.html Apache License] is known for protecting users against patent suing. | ||
*[http://opensource.org/licenses/MIT MIT License] | *[http://opensource.org/licenses/MIT MIT License] Similar to BSD - permissive, and doesn't hold you liable. | ||
*[http://opensource.org/licenses/ISC ISC License] is like BSD/MIT but clearer given that there is one ISC license and like 6 BSD/MIT licenses, and that no one knows what the fuck an Expat is. The license used by OpenBSD. | *[http://opensource.org/licenses/ISC ISC License] is like BSD/MIT but clearer given that there is one ISC license and like 6 BSD/MIT licenses, and that no one knows what the fuck an Expat is. The license used by OpenBSD. | ||
*[https://en.wikipedia.org/wiki/WTFPL WTFPL] - DO WHATEVER THE FUCK YOU WANT TO PUBLIC LICENSE. The name says it all. | *[https://en.wikipedia.org/wiki/WTFPL WTFPL] - DO WHATEVER THE FUCK YOU WANT TO PUBLIC LICENSE. The name says it all. | ||
| Line 12: | Line 12: | ||
¹ [http://www.gnu.org/licenses/license-recommendations How to choose a license for your own work] | ¹ [http://www.gnu.org/licenses/license-recommendations How to choose a license for your own work] | ||
² [http://www.choosealicense.com Github's how to choose a license page] | |||
Revision as of 01:29, 20 October 2015
Licenses
There are multiple kinds of licenses that software can be released under.
- GNU GPL is what GNU/Linux is released under. Essentially, you are free to do what you want with software released under this code, provided that if you release it to the public you must also release the source code. Source code does not have to be released if binaries to modifications are not released to the public. Think of it as a license that grants you every freedom, except the freedom to take away other people's freedom over the software. This license highly favors the end users.
- GNU AGPL is what the FSF suggests for server software.¹ Essentially, it is the GPL with a additional clause that people accessing the software over a network must also get the source. With the popularity of "cloud" services, GPL software can be changed and run at a server without the obligation to release the source code. This license highly favors the end users.
- BSD License is much more permissive than the GPL. You basically can do anything you want. You can even incorporate BSD-licensed code in your closed-source proprietary software, effectively re-licensing the source code, so long as you give the original author(s) credit as appropriate.
- Apache License is known for protecting users against patent suing.
- MIT License Similar to BSD - permissive, and doesn't hold you liable.
- ISC License is like BSD/MIT but clearer given that there is one ISC license and like 6 BSD/MIT licenses, and that no one knows what the fuck an Expat is. The license used by OpenBSD.
- WTFPL - DO WHATEVER THE FUCK YOU WANT TO PUBLIC LICENSE. The name says it all.
- CC-BY
- CC-BY-SA - Without the no commercial and no modifications additions, this is a very liberal license. Anyone can use or modify this work, as long as they let others use it and attribute the author. This license lends itself to art better than it does to software.
¹ How to choose a license for your own work ² Github's how to choose a license page