Which is an improvement of the GPLv2 license?
The GPLv3 is an improvement of many aspects of the GPLv2 (making a case against DRM, software patents…), which is what the AGPL is based on.
Where can I find the GNU GPL Version 2?
Check out some of our other licensing resources or contact the Compliance Lab at [email protected]. This page contains answers to commonly asked questions about the GNU General Public License (GPL), version 2.
When is a GPL license incompatible with a module?
If license for a module Q has a requirement that’s incompatible with the GPL, but the requirement applies only when Q is distributed by itself, not when Q is included in a larger program, does that make the license GPL-compatible? Can I combine or link Q with a GPL-covered program?
Can a piece of software obtained under the GNU GPL be modified?
If I use a piece of software that has been obtained under the GNU GPL, am I allowed to modify the original code into a new program, then distribute and sell that new program commercially? How does the LGPL work with Java? Could you give me step by step instructions on how to apply the GPL to my program?
When does your software need to be covered by the GPL?
If you release/distribute software containing GPL’d components (such as statically linked libraries), your software must be covered by the GPL. (This is the impression given for version 2; version 3 may be different.)
Can a GPL library be distributed for commercial use?
You can distribute your application using a GPL library commercially, but you must also provide the source code. GPL v3 tries to close some loopholes in GPL v2.
Which is an example of the limitation of GPLv2?
Well, it’s the ‘Cake as a Service’ example. The limitation of GPLv2, is that it states that whoever has one freedom — like the ability to run the code, they’ll have all four freedoms. But when it comes to SaaS, the loophole is that users of a SaaS don’t run the code.