Earlier quoted context omitted.
AGPL tries to do this but it's otherwise similar to GPL rather than Apache 2.
AGPL in no way prevents anyone to use the licensed software. It just demands, like GPL, that modifications be made available to users, but in addition to GPL, extends this duty to the case where the licensed software is used remotely/as a service (rather than "distributed" to users for use on their own computer).
AWS forked my project and launched it as its own service
671–673 of 673 posts
Re: AWS forked my project and launched it as its own service
#672"free software for me but not for thee"
I'd actually support a license that said "it's OSS except Google/Amazon can't take my thing, launch as a service and charge for it".
If fact someone should come up with a well written licence that adds conditions when the licensee revenue is over a certain (large) amount, like say royalties. Everyone should be happy with that.
Re: AWS forked my project and launched it as its own service
#673I run the open source strategy and marketing team at AWS. As I told Tim privately and publicly ( https://twitter.com/mjasay/status/1317084448119169024 ), I hadn't been aware of this but am talking with the relevant product team to see how we can improve in his regard. AWS uses a lot of open source, and we contribute a lot, both in terms of code (first-party projects like Firecracker and Bottlerocket, but also third-p…