3 ms·
The vague answer to the first part is: whatever code you would've been required to include if the library were GPL and you "distributed" an application using it
by _delirium 15y ago
The vague answer to the first part is: whatever code you would've been required to include if the library were GPL and you "distributed" an application using it, which is any portion of the software that can be considered a "derivative work" of the library. The AGPL only changes the definition of "distributed" to include running it as a hosted webapp, but doesn't meddle with the definition of "derivative work".
Some cases are easier than others, and I think A is definitely too strong; for example, if your company runs two clearly separate webapps, and one of them is a derivative work of AGPL code while the other isn't, you only need to AGPL the one of them. One possibility is to run your planned source release by the author of the AGPL code in question, and see if they feel your course of action satisfies their intent with the license.
- nsxwolf 15y agoThanks. Reading the license they seem to say the intent is to have to "give something back" for using the code. If we were to release just the portion of the code that uses it, I feel that it would serve as an excellent real-world example of the use of this library which would be helpful to many. But honestly, if there's an alternative to this library with a different license I'm more inclined to do that out of fear of compliance failures. Not against paying for software either, but this particular vendor doesn't advertise a price - they want to basically sit down and have a chat with you about how you use the library. That sounds like $$$$ to me, no doubt they will want to get into details about number of processors and threads and users and price accordingly.