3 ms·
I think the author is misreading Google's policy (https://opensource.google/docs/using/agpl-policy/ https://opensource.google/docs/using/agpl-policy/). They're
by SpicyLemonZest 6y ago
I think the author is misreading Google's policy (https://opensource.google/docs/using/agpl-policy/ https://opensource.google/docs/using/agpl-policy/). They're not saying that communications over the internet constitute a linkage, they're saying that:
* Because of free and open development practices within Google, it's impractical for developers to be constantly aware of what libraries get linked into their binaries. (This is exacerbated because of their monorepo, but even in a multi-repo setup it's very easy to end up with random libraries in your dependency chain.)
* If an AGPL library did end up linked, because all Google's services are accessible through a remote network, the virality provisions kick in and they might have a legal duty to distribute the entire binary.
* Therefore, they have to ban AGPL libraries so that no core service developer accidentally depends on one.