Contents
Do you have to license derivatives under AGPL?
As per usual with GNU licenses, you must license derivatives under AGPL. It provides the same restrictions and freedoms as the GPLv3 but with an additional clause which makes it so that source code must be distributed along with web publication.
Why do I need Source code for AGPLv3?
The objective was to close a perceived loophole in the ordinary GPL in environments where users make use of functionality provided as a web service, but no distribution of the code providing the functionality occurs.
How does the AGPL license differ from other GNU licenses?
The AGPL license differs from the other GNU licenses in that it was built for network software. You can distribute modified versions if you keep track of the changes and the date you made them. As per usual with GNU licenses, you must license derivatives under AGPL.
Can you use AGPL libraries with closed source software?
If we follow the comments it turns out that you can use AGPL libraries with your closed-source, commercial server-side software, as long as you don’t modify the library. Is that the case? Or you have to distribute your entire application when you use an AGPL licensed library?
Do you have to license GPLv3 source code?
If you use components that are licensed under GPLv3, then you are required to license the complete application the contains the GPL components under the GPL as well. However, this is not all bad news, because the GPL only requires that you distribute the source code only to those persons that you distribute the binary to.
Do you have to give GPL source code away?
However, this is not all bad news, because the GPL only requires that you distribute the source code only to those persons that you distribute the binary to. If you never distribute the software to anyone, then you are also not required to give the sources away.