Tried to ask this on SO but was referred here…
Am I correct in saying that using a GPL'ed web application framework such as Composite C1 would NOT obligate a company to share the source code we write against said framework?
That is the purpose of the AGPL, am I correct?
Does this also apply to Javascript frameworks like KendoUI?
The GPL would require any changes that we make to the framework be made available to others if we were to offer it for download.
In other words, merely loading a web sites content into my browser is not "conveying" or "distributing" that software.
I have been arguing that we should avoid GPL web frameworks and now after researching I am pretty sure I am wrong but wanted to get other opinions?
Seth
Best Answer
AGPL and GPLv3 were created to close the "GPL as a service" loop hole. If the code is licensed this way and you are going to use the web server in a commercial setting I would look elsewhere.
I am not a lawyer, etc.
Affero General Public License
AGPL is the opposite of what you are assuming here.
You cannot use KendoUI GLPv3 license unless your whole product that is using it is also GPL compatible.
In GPLv3 and AGPL it is conveying and distributing.
These questions come up time and time again. We can apply logic and reasoning to most of the products in question. Kendo UI has a commercial version of the product available and a GPLv3 version available. It stands to reason that they do not want you using their product in a commercial settings, i.e. a non GPL application, unless you pay for it.
They even spell it out on their web page: