3 ms·
If I understood it correctly, if you change the code of SŌZU, you need to open-source not only your fork, but everything that can be reached/connected to by SŌZ
by hpb42 4y ago
If I understood it correctly, if you change the code of SŌZU, you need to open-source not only your fork, but everything that can be reached/connected to by SŌZU.
Google has a policy against using APGL internally, nor in your company equipment[0].
The primary risk presented by AGPL is that any product or service that depends on AGPL-licensed code, or includes anything copied or derived from AGPL-licensed code, may be subject to the virality of the AGPL license. This viral effect requires that the complete corresponding source code of the product or service be released to the world under the AGPL license.
[0] https://opensource.google/documentation/reference/using/agpl-policy/ https://opensource.google/documentation/reference/using/agpl...
- jacooper 4y agoI don't think this true, the idea is that it triggers the same-license requirement even for network accessible code. Where normal GPL only triggers that when the code is distributed, which allowed the SAAS loophole to exist. As for the spreading to other programs part, yes that's the entire point, if you use free code, anything built on it should be free too, to continue giving to the Free/open Eco system.