9 ms·

I think you're looking at it too broadly. The AGPL's intent is to extend GPL protection for software available on the network, see the FSF's blog post here: ht

I think you're looking at it too broadly. The AGPL's intent is to extend GPL protection for software available on the network, see the FSF's blog post here: https://www.fsf.org/bulletin/2021/fall/the-fundamentals-of-the-agplv3 https://www.fsf.org/bulletin/2021/fall/the-fundamentals-of-t... > Simply put, the AGPLv3 is effectively the GPLv3, but with an additional licensing term that ensures that users who interact over a network with modified versions of the program can receive the source code for that program The text you are referencing is present in the GPL too, and it doesn't make GPL code infect adjacent apps.

josephcsible 4y ago
> It's not like the AGPL infects everything on your network, it's limited to the original source. Indeed. By the way, the difference between the AGPL and the SSPL is that the SSPL does infect your entire stack and isn't limited to just the original source, which is exactly why the AGPL is free and open-source but the SSPL is neither.
raggi 4y ago
Now consider the "Tivo" target, which is that the scripts and tools required to deploy the code are things they absolutely want to cover. You didn't answer my question directly though (and nor does the linked article), what is it about deploy in your usage that is materially different from "install" in the text? Do you disagree that the device case is covered? How do you consider a cloudy type environment different, and by what definition and justification? What if I sell the deployment in a box for on-prem, as well as in hosted VMs? Does that change users rights under the license?