|
|
|
|
|
|
by Eridrus
3545 days ago
|
|
|
My layman's understanding of the AGPL was that it essentially extends the concept of linking to connecting to the software that interacts over the network, so that you can't do something like take a library, wrap it in a microservice and just call the microservice in your product without opening your entire software stack to AGPL claims. Maybe I am misunderstanding it, but I would want a lawyer to tell me that before using any AGPL code. |
|
|
My understanding is that it somewhat extends the concept of "distributing" to providing remote access over a network:
"Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.
Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License."