4 ms·
> they've put a lot of pressure to change the default license for new projects from (A/L)GPL to ASL How have they put pressure? I've written some libraries pe
by dehrmann 6y ago
> they've put a lot of pressure to change the default license for new projects from (A/L)GPL to ASL
How have they put pressure?
I've written some libraries personally and licensed them under the Apache or BSD license because I want it to be helpful for anyone who needs it. I'm really not concerned if they make money off it or not or if they contribute back.
If you're talking larger projects, a lot of the big, recent ones have come out of companies--projects like MongoDB, Cassandra, React, Kubernetes. Some like Hadoop were inspired by work at big companies.
- est31 6y agoGoogle literally can't even use something that's AGPL licensed due to internal policy. Apple has a war on GPL, shipping outdated versions of GNU tools that still have GPLv2, and funding clang development which has a non-copyleft license.
- heavyset_go 6y agoFor reference, here is Google's AGPL policy: https://opensource.google/docs/using/agpl-policy/ https://opensource.google/docs/using/agpl-policy/ As an advocate of the AGPL, and someone who releases software under it, I think Google's argument is pushing FUD.
- bigbubba 6y agoGoogle refusing to use AGPL software actually makes the license more appealing. The way AGPL wards off corporations like google is almost as though it has a 'do no evil' clause.
- jimktrains2 6y ago> I've written some libraries personally and licensed them under the Apache or BSD license because I want it to be helpful for anyone who needs it. I'm really not concerned if they make money off it or not or if they contribute back. It's not about getting contributions back, but ensuring that everyone who needs it can use it includes end users.
- TeMPOraL 6y agoIndeed. Permissive licenses are about protecting the rights of developers; free software licenses are about protecting the rights of end users.