License
Jump to navigation
Jump to search
GPL
from https://en.wikipedia.org/wiki/GNU_General_Public_License#Linking_and_derived_works
According to the FSF, "The GPL does not require you to release your modified version or any part of it. You are free to make modifications and use them privately, without ever releasing them."[64] However, if one releases a GPL-licensed entity to the public, there is an issue regarding linking: namely, whether a proprietary program that uses a GPL library is in violation of the GPL. This key dispute is whether non-GPL software can legally statically link or dynamically link to GPL libraries
And more
The Free Software Foundation (which holds the copyright of several notable GPL-licensed software products and of the license text itself) asserts that an executable that uses a dynamically linked library is indeed a derivative work. This does not, however, apply to separate programs communicating with one another.[65] The Free Software Foundation also created the LGPL, which is nearly identical to the GPL, but with additional permissions to allow linking for the purposes of "using the library".
see also https://en.wikipedia.org/wiki/GPL_linking_exception
And more,
Affero and GNU Affero General Public License (AGPL) extend the restriction to software that runs on network. From https://en.wikipedia.org/wiki/GNU_Affero_General_Public_License
[AGPL ]It is intended for software designed to be run over a network, adding a provision requiring that the corresponding source code of modified versions of the software be prominently offered to all users who interact with the software over a network.[6]
See also:
- license compatibility graphs:
https://dwheeler.com/essays/floss-license-slide.html
http://gkapi.blogspot.com/2016/09/foss-license-compatibilities.html
- compatibility checker: