 |
| One user recommended this comment. What they said: |
|
jkaplowitz Jul 27, 2020 | on: The terms of the AGPL are pretty easy to comply with | context
Thanks for having publiished these policies publicly! You gave a pretty clear summary of Google's motivations for banning AGPL on HN five and three years ago two of the previous times this came up, and having worked at Google 2011-2015 (including some interactions there with you), your public explanations of why from back then are extremely credible and rational given the logistics of what's easy and hard inside Google. https://news.ycombinator.com/item?id=9956542 https://news.ycombinator.com/item?id=13979443 Not that I'm surprised, as you've always been pretty forthright and honest. Thanks for continuing to be that way. |
| Also recommended by people who recommended this: | ||
| 1. | “We don't allow AGPL.” (comment) | |
| recommended by 1 user | 2015 | DannyBee on: Why I am pro-GPL | original thread | | ||
Errr,it's completely and totally unrelated to that. It's because we have tons of temps, vendors, and contractors, and don't want to have to owe them source code to internal systems. The other alternative (remember that google is a monorepo) would be to somehow police them differently. That is literally not worth the cost.