5,337
edits
No edit summary |
|||
Line 57: | Line 57: | ||
==General Public License (GPL)== | ==General Public License (GPL)== | ||
This is referred to as a copy-left license.<br> | This is referred to as a ''copy-left'' license.<br> | ||
All derivatives and extensions of this program must use the same license. | All derivatives and extensions of this program must use the same license. | ||
===GPLv2=== | ===GPLv2=== | ||
Basically any derivatives of the program must be open-source to whoever can obtain the binaries. | |||
E.g. if you sell a device running your custom linux kernel, you must open-source your custom linux kernel. | |||
===GPLv3=== | ===GPLv3=== | ||
Line 74: | Line 75: | ||
Same as GPL but you can dynamically link to it from proprietary software.<br> | Same as GPL but you can dynamically link to it from proprietary software.<br> | ||
However, you must provide source for the version of the library you are using. | However, you must provide source for the version of the library you are using. | ||
===AGPL=== | |||
[https://www.gnu.org/licenses/agpl-3.0.en.html APL 3.0] | |||
The GNU Affero General Public License is basically GPL but where interaction over the network counts as distribution. | |||
So if people can interact with your AGPL program over the internet, then you must open-source it. | |||
==Resources== | ==Resources== | ||
* [https://opensource.stackexchange.com/questions/217/what-are-the-essential-differences-between-the-bsd-and-mit-licences BSD vs MIT License stackexchange] | * [https://opensource.stackexchange.com/questions/217/what-are-the-essential-differences-between-the-bsd-and-mit-licences BSD vs MIT License stackexchange] |