3 ms·
> Given how long she has been doing this, I would simply not believe that she missed any of the issues I mentioned (the ambiguity, the AGPL/GPL/etc issues). Ag
by Boulth 8y ago
> Given how long she has been doing this, I would simply not believe that she missed any of the issues I mentioned (the ambiguity, the AGPL/GPL/etc issues).
Agreed on that, based on just reading one of her books. I wonder why didn't they choose AGPL.
- sciurus 8y agoIt looks like they were using AGPL before, but now they are switching to Commons Clause. See the history of the RedisSearch license, for example. https://github.com/RedisLabsModules/RediSearch/commits/master/LICENSE https://github.com/RedisLabsModules/RediSearch/commits/maste...
- Boulth 8y agoYep, now I see this vague explanation on https://commonsclause.com https://commonsclause.com : > Why not AGPL? > The AGPL was drafted in a different era where Cloud ecosystem was not nearly as well-developed. After deep legal analysis, many of the AGPL’s features were determined to be insufficient towards some of the requirements modern projects face. > For example, much of the value for cloud-based software comes outside of the actual code (i.e. hosting) thereby nullifying many of the incentives to enforce source-availability. In addition, many of the AGPL's features can be more restrictive towards an end user that wishes to incorporate software into a new work, which makes a source-available license with additional grants more permissive.