Earlier quoted context omitted.
>this big co strategy of "mine. I profit now. everyone who built up this useful thing can suck eggs" really sucks and sucks for the humans and sucks for Open Source. Then use a different license. Hoping that a company like Amazon finds it in their hearts to always do what _you_ consider "the right thing" is just a loser of a strategy. You seem to want all of the good of open source, with none of the downsides. Good l…
"Don't like how shitty people can be? I don't care" - that is how this kind of comment reads. But let's move on. Interesting idea for a license. Everyone can use and modify it, but if a large company with a market cap above $100m or a company wholly funded or owned by such company decides to utilize this project as a for-profit service, then said large company must hire me at for no less than $175,000 in 2020 value.
AWS forked my project and launched it as its own service
491–500 of 673 posts
Re: AWS forked my project and launched it as its own service
#492Earlier quoted context omitted.
Ah, yes, he is acknowledged in a text file that almost no one will read. Obviously there is no legal requirement, but would it be that hard for Amazon to include a "forked from..." or "built off of...", etc. to the announcement and product pages, if it really is heavily based off of another work?
Can you show me an example of any other project released from FAANG doing that? Curious what the expectations are.
This whole thing is very reminiscent of the Occupy Wall Street movement. People are very sensitive to the injustices they perceive themselves as having to endure especially in relation to those wealthier than them. But where's the willingness to jump out of local scope and apply the same principle globally (and reflexively)? It seems to be absent.
Re: AWS forked my project and launched it as its own service
#493I really wish, that when COs like Amazon decided to productize a thing they either offered the core developer(s) enough $ to work on it full time (if they wanted) or a job to do that with a guarantee that as long as it was a product, and they wanted to work on it, they'd be allowed to continue. Problem with offering job is the likelyhood of getting redirected to some other unrelated work. instead of forking they coul…
>this big co strategy of "mine. I profit now. everyone who built up this useful thing can suck eggs" really sucks and sucks for the humans and sucks for Open Source. Then use a different license. Hoping that a company like Amazon finds it in their hearts to always do what _you_ consider "the right thing" is just a loser of a strategy. You seem to want all of the good of open source, with none of the downsides. Good l…
Re: AWS forked my project and launched it as its own service
#494Situations like this make me wonder why no one has created an open source license with a clause excluding multi billion dollar companies. If your company makes more than, say, $50 billion in revenue per year or something crazy like that, then you need to pay for a license. Everyone else can use the free license. Amazon in particular is well known to be aggressively anti-competitive, as we saw with the Diapers.com fia…
Polyform Shield is what you're looking for https://polyformproject.org/licenses/
I really do think we need a couple of new licenses along these lines to become popular enough to be generally accepted. Having said that, I struggle to really grok the language in these licenses; it could be that I'm just more familiar with MIT, BSD and the like, but with the Polyform licenses I'm always left with questions about what I can and can't do.
Re: AWS forked my project and launched it as its own service
#495Earlier quoted context omitted.
Like CC-BY-NC (Creative Combine, Attribution, Non-commercial). If you want to use the work commercially (ie for business purposes, commercial doesn't require selling) then you must negotiate licensing terms (or infringe copyright [Fair Use / Fair Dealing aside].
Please don't encourage or suggest the use of CC anything for code. It just wasn't designed for code and creates huge ambiguities on the rights you intended. https://creativecommons.org/faq/#Can_I_use_a_Creative_Common... As stated on the Creative Commons website (licensed under CC-BY): Can I apply a Creative Commons license to software? We recommend against using Creative Commons licenses for software. Instead, we st…
>Instead, we strongly encourage you to use one of the very good software licenses which are already available
But as far as I am aware, there are no comparable software licenses that prohibit commercial use. So, the CC NC licenses seem to be the only option here, even if supposedly imperfect.
Do you have an example of an ambiguity with regard to non-commercial use?
Re: AWS forked my project and launched it as its own service
#496I really wish, that when COs like Amazon decided to productize a thing they either offered the core developer(s) enough $ to work on it full time (if they wanted) or a job to do that with a guarantee that as long as it was a product, and they wanted to work on it, they'd be allowed to continue. Problem with offering job is the likelyhood of getting redirected to some other unrelated work. instead of forking they coul…
> this big co strategy of "mine. I profit now. everyone who built up this useful thing can suck eggs" really sucks and sucks for the humans and sucks for Open Source. I think the software community is having an "I never thought the leopards would eat my face" moment. The community pushed for a long time for licenses that donated labor to corporations because the licenses sounded more "free", and that flattered their…
Re: AWS forked my project and launched it as its own service
#497Earlier quoted context omitted.
I would bet AWS wouldn’t even touch it if it was under GPL, most companies have made it forbidden to use because of reasons you stated.
And would that be a bad thing? If the tool is good, FOSS users will get a competitive advantage over AWS.
Re: AWS forked my project and launched it as its own service
#498I really wish, that when COs like Amazon decided to productize a thing they either offered the core developer(s) enough $ to work on it full time (if they wanted) or a job to do that with a guarantee that as long as it was a product, and they wanted to work on it, they'd be allowed to continue. Problem with offering job is the likelyhood of getting redirected to some other unrelated work. instead of forking they coul…
> this big co strategy of "mine. I profit now. everyone who built up this useful thing can suck eggs" really sucks and sucks for the humans and sucks for Open Source. I think the software community is having an "I never thought the leopards would eat my face" moment. The community pushed for a long time for licenses that donated labor to corporations because the licenses sounded more "free", and that flattered their…
Re: AWS forked my project and launched it as its own service
#499I 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…
Re: AWS forked my project and launched it as its own service
#500Earlier quoted context omitted.
I would bet AWS wouldn’t even touch it if it was under GPL, most companies have made it forbidden to use because of reasons you stated.
FYI: Linux is licensed under GPL v2. AWS uses Linux extensively.
These are, honestly, expensive questions to answer as the tech gets more complicated - at what point is linux part of the binary you're distributing vs. an external dependency and, if you get the answers wrong, you'll potentially create an outage that will wreck havoc on the economy by grinding the cloud to a halt and cost Amazon tens of billions in revenue.
This is a very, very, complicated situation.