"When the service launched, imagine our surprise when the Amazon CTO tweeted that the service was released in collaboration with us. It was not. And over the years, we have heard repeatedly that this confusion persists. NOT OK."
"So imagine our surprise when Amazon launched their service in 2015 based on Elasticsearch and called it Amazon Elasticsearch Service. We consider this to be a pretty obvious trademark violation. NOT OK."
"When Amazon announced their Open Distro for Elasticsearch fork, they used code that we believe was copied by a third party from our commercial code and provided it as part of the Open Distro project. We believe this further divided our community and drove additional confusion. "
This just means their CTO was sloppy, Amazon legal department would have never allowed that tweet.
> "So imagine our surprise when Amazon launched their service in 2015 based on Elasticsearch and called it Amazon Elasticsearch Service. We consider this to be a pretty obvious trademark violation. NOT OK."
This is a trademark violation indeed though IANAL, it doesn't require a change to the license to attack them for that. Definitely an abuse of power by Amazon though, completely not ok as they don't care about paying a fine for that, they have all the money in the world. But again, not related to the license thing.
> "When Amazon announced their Open Distro for Elasticsearch fork, they used code that we believe was copied by a third party from our commercial code and provided it as part of the Open Distro project. We believe this further divided our community and drove additional confusion. "
Elastic was known to mix proprietary and open source code and it got to a point where few people knew what was open source and what was not. Many people were not happy with this situation and elastic.co was abusing the situation to charge paid licenses as people were scared of using proprietary code without knowing. The work amazon did to remove all proprietary code from they fork was actually welcomed by the community though I'm not surprised they missed some as it was really hard to tell.
And Elastic tried going the legal route:
https://searchaws.techtarget.com/news/252471650/AWS-faces-El...
It sounds like their whole issue was about confusion in the marketplace, though, and when someone does an oopsie that results in that kind of confusion, it may not be enough to take care of it quietly, on the side. So it seems now Elastic is making more noise, in an effort to clarify things more publicly.
Surely the legal department would have issued some sort of retraction. Can you find it?
>Definitely an abuse of power by Amazon
Yeah, that's what we're saying.
>people were scared of using proprietary code without knowing...I'm not surprised they missed some as it was really hard to tell.
Amazon is a trillion dollar company that has every capability of doing their due diligence. Sloppy communication, abuse of trademarks and stealing proprietary code are all inexcusable behaviors by a company with the size and power that Amazon has.
You're describing the problem as if it were the excuse. Amazon abused their power, stole proprietary code, abused a trademark, and violated the culture of the open source community whose code they were leveraging for profit. There's no excuse for it, even if it was somehow legal - and I don't suspect it was. I suspect that Amazon knows it's not legal - they just figure they can get away with it.
Sure, but we are not talking about "the intern tweeted something incorrect, gather your pitchforks until they delete it".
We are talking about a prolonged time span where AWS completely abused their massive size and market tower to basically do the legal and PR equivalent of laughing in the face of another company they were using and abusing. Details aside, that is a pretty grim view for the world of software, no?
But the tweet is still up: https://twitter.com/Werner/status/649738362086027265 (archive: https://archive.is/0py42)
Pretty sure legal has reviewed it like a 100 times by now: AWS' taking no prisoners here.
1. Delete it with an apology (admitting guilt is not likely to be great for the lawsuit).
2. Delete it and say nothing (destruction of evidence is not likely to be great for the lawsuit).
I don't understand. If I have an ISP and I offer mysql servers, can't I call that offering "Eznzt MySQL Service"?
A long time ago I had an open source project to manage mysql replication topologies, and I called it mysql-ha. At some point, they reached out to me about the trademark infringement.
They were nice about it, I did not get a legal notice or anything, just a contact from a MySQL employee pointing me to their policy (as in my response to your example: I could have called it ha-for-mysql), and requesting that I changed the name to make it compliant. I ended up with a full rename (called it highbase) and they were kind enough to give me a one year free subscription to MySQL Enterprise as a token of appreciation for my change.
In way that I think is interesting regarding the AWS and Elastic situation, what MySQL's trademark policy intended was to avoid the situation in which a third party could be confused by a product or project name (mysql-ha in my case) as to believe that MySQL, the company, was behind the offering. So any use of the trademark that made it clear they were not involved (as in the "X for MySQL" vs. "MySQL X") was ok.
Amazon sells Hershey bars through its site. I don’t think it needs to get permission to say “here’s the subscribe and save service to buy Hershey bars.”
I think the confusion is whether ElasticCo is endorsing or part of the service offering. So it should be clear that the offering isn’t by ElasticCo.
Back to the chocolate example, as long as Amazon doesn’t make it seem like Hershey is endorsing their site or offering the product they should be clear. I’ve seen this tucked into the fine print on stuff where it says that just because they are selling Hershey it has nothing to do with Hershey the company.
It seems odd that the company wouldn’t want it to be called AWS ElasticSearch as that’s what it is. ElasticSearch software sold as a service by AWS. Calling it something else is more confusing.
Personally, I find that thinking about this issue seems more intuitive when imagining tangible physical products. Imagine that Amazon decides to enter the Cookies as a Service market, and starts launching service offerings with names like 'Oreos by Amazon'. At a glance, would one not assume that this was some sort of collaborative effort between Nabisco and Amazon? I think the average consumer would. And the same probably applies in a situation involving a software product.
Specifically to your example (I think), see "Company, Product or Service Names ", where it states the following:
> Do not use Oracle trademarks or potentially confusing variations as all or part of your company, product or service names. If you wish to note the relationship of your products or services to Oracle products or services, please use an appropriate tag line as detailed above. For example, "XYZ for Oracle database" not "OraXYZ or XYZ Oracle"
[1]https://images.law.com/contrib/content/uploads/documents/403...
[2]https://www.courtlistener.com/recap/gov.uscourts.cand.347725...
And yeah, "Amazon Elasticsearch Service" completely fooled me for about a week until Google searches revealed enough about how elastic.co isn't just a site promoting Elasticsearch, but was a provider of instance configuration.
I mean, sure. Someone can poop on the lawn.
There is a difference between that, and some business coming along with a dump truck full of shit that they then dump on the lawn, and I'm sure you understand that.
Whats happening is they’re selling the same product; legally they’re entitled to do so.
They’re selling it in a deceptive (perhaps even legally dubious way), and thats not ok; but forget that, this has nothing really to do with being the good guys for open source and amazon being the bad guys, thats just the narrative that the elastic PR folk are putting out.
What’s happening here is being out-competed by people selling the same product, because despite being technically inferior (in my view) the competition can sell more of it more cheaply and not really care about the margins.
So... yes, I’m sympathetic, but this PR dance we go through every time pains me.
Just say it: we’re struggling. We cant compete with Amazon on equal terms, so we’re changing the license to force them to pay us royalties, or stop selling it.
You’re not doing it from the goodness of your heart, and if amazon wasn’t kicking your ass, you wouldn’t care, you’d just be laughing at them “trying to run a cloud version of elastic, ha!”. ...but amazon is very very good at that, actually, and very good at selling it.
Who’s going to judge you for not having amazons scale? No one; but they’re not being dicks, they’re doing their jobs, very successfully.
If you don’t like losing, that’s perfectly ok, no one does... but it doesnt make them bad, it just means they’re better at it than you.
Changing things to preserve your competitive edge is totally ok; but I don’t think its right to spin this us-them AWS is the evil empire narrative; youre in this situation because of the decisions you made, take a bit of humble pie and acknowledge responsibility for it as well.
Why do we need to forget the trademark infringement?
If Amazon is engaging in trademark infringement, lying about their connection\collaboration with the trademark holder, and including commercially licensed technology in an open source fork of a project, they are acting very poorly. Your argument of Amazon just being able to execute better falls flat if these facts are true and it means they're cheating, and that deserves some recognition.
Because that’s what the license they used said.
Is there a difference? The sign never said how much shit could be deposited on your lawn.
If elasticsearch had this license from day one, that would be fair enough, but many people do not freely contribute time and effort to improving something which is not freely available to all others (whether individual or large corporation).
Elasticsearch is self-victimising here when they are arguably exploiting FOSS contributors good will (though due to the CLA what they are doing is most definitely legal).
Does AWS ever contribute anything that isn't an AWS integration? I'm not asking rhetorically -- those are the only kind of "contribution" I've ever seen from them.
None of the above appear to be related to AWS specific APIs and offer a small sample of total contributions from AWS employees.
Seems to me that Amazon has grossly overstepped fair play here.
I fully support their right to change their licensing, and I understand they may not have thought through the implications of their license -- and I empathize with that. I also empathize with criticism that Amazon isn't doing a great job of supporting the ecosystem that supports them, it would be nice if they did more. And it goes without saying, but I also strongly empathize with the frustration about the borderline trademark infringement that's happening here. That's a completely separate problem.
But I don't like the implication that Open Source licenses are a legal technicality rather than a specific philosophical choice to allow reuse. People don't need to feel guilty about following Open Source licenses, the idea is to encourage reuse -- even by corporations.
We do harm to that movement when we try and backtrack from that philosophy or say, "sure, you have the legal right to reuse the code, but we're going to try and implement social/technical barriers to you doing so." There are plenty of decent source-available licenses projects can use if that's their intent. They carve out exceptions for small-scale reuse while trying to limit companies like Amazon from capitalizing on the ecosystem. And maybe more projects should use those licenses since they more accurately reflect the outcomes that the authors seem to want. There's nothing wrong with having projects that allow only small-scale reuse.
But if someone releases their project as Open Source I'm going to treat it like Open Source, because that's what the movement is about, and trying to reverse the legal progress we've made by constructing new moral barriers in front of reuse is harmful to that movement. When we say that people have a moral right to reuse, adapt, and share our code, we mean it.
But the point of Open Source is that reciprocity of code/money/value is not required. That's literally the scenario that many of us are trying to build.
It feels like the difference here is that you're looking at "someone builds a giant public hosting service off of our code" as an immoral end. But I'm saying that's not immoral, that is an acceptable result.
It's obviously not the result Elastic wanted, and I empathize with that, but... I don't know, maybe we need to educate people more about what Open Source actually means. Maybe we need to encourage more people to use source available licenses if there's a disconnect in how people understand the actual goals of the movement.
We believe that people have an intrinsic, moral right to share and reuse code. Not just good citizens who help build up the system and support us -- everybody.
(I also don't like Elastic as a company, to be clear, and wouldn't shed many tears if they disappeared tomorrow, there's just a hierarchy of dirtbags and they're not near the top.)
As far as encouraging those source-available licenses--that sounds great, except that, in my experience, people with the temerity to offer source-available licenses get treated like shit anyway because they aren't giving away the farm. So I don't know where we go there, either.
I don't know what else I can do as an Open Source developer in my projects and my terminology to imply that when I say, "you can reuse my code for any reason" I actually mean it. I guess traditional Open Source advocates could abandon the entire term and go off and create a brand new movement where we try to make that even more explicit, but people are just going to follow us there and then try to coopt the term again.
> people with the temerity to offer source-available licenses get treated like shit anyway because they aren't giving away the farm
I will call out people who are doing that.
But really, the only comments I have about source available products are:
A) they don't offer all of the advantages of Open Source (although they offer many more benefits than fully closed-source software), and I think that pointing that out is not a moral judgement, just a statement of fact about what the licenses do and do not allow.
B) people who offer source available licenses need to stop saying that they're basically the same as Open Source, or that they're just a subset of Open Source, or that they exist because Open Source has lost its way.
Because the licenses are not the same. All other debates aside, both us at this point in the conversation recognize this, right? You and I are disagreeing about a fundamental philosophy on what rights and moral responsibilities people have around code. You fundamentally disagree with me about whether or not large companies have the right to completely freely reuse permissive code, or whether they have an obligation to pay for it. That disagreement is so large that it affects our attitudes about whether offering large-scale commercial hosting of an Open Source product is moral.
And it's fine that you and I disagree on that point, but we can look at that disagreement and say that clearly your goals when licensing software are different than mine. So to me, it seems pretty reasonable that people who have this fundamental disagreement with the OSI should acknowledge that instead of acting like the Open Source movement is broken. It's not broken, it disagrees with you about the goals are in making code available to other people.
It's not people being stubborn, it's not that the OSI doesn't understand the consequences of Open Source, it's that it does understand the consequences of Open Source and it disagrees with you about what consequences are desirable. The Open Source movement doesn't need shared source advocates to 'save' us, we need them to acknowledge that their goals are different than ours.
Any code that is GPL licensed is Open Source. It might be distasteful to some people to force contributors to sign a CLA, you might get some criticism from some segments of the community, but it's not problematic in a way that means it's fundamentally non-FOSS.
BSL on the other hand is not Open Source, but becomes Open Source at the point where the BSL license expires and is replaced by an Open version.
----
Personally, I might get some pushback on this, but I actually kind of like BSL more than dual licensing. Dual licensing relies on the fact that people find the GPL toxic. It feels much more to me like a temporary solution, and one that only works by kind of dragging the GPL through the mud. Even among people who don't hate the GPL, it encourages them to think of it as a tool to enforce 'fairness', rather than as a complicated way to use copyright to push towards a world where every user has the rights guaranteed in the GPL for every program they run.
TBH, I vaguely suspect that some of the movement towards SSPL is an evolution of people's attitude towards dual licensing, where they thought that the un-attractiveness of the GPL was the point of the GPL, and now feel like it's not living up to it's 'promise'. The fact that Amazon is able to use GPL code to provide commercial services is seen by those people as a bug, not a feature.
Many of the downsides and restrictions around community contributions with BSL are also present in dual licensing because of the implicit CLA requirements in dual licensed projects. So it's not clear to me that BSL is more harmful to community-built software than dual licensing, and given the above trend, it seems a bit more honest (for lack of a better word).
Because dual licensing doesn't really affect companies like Amazon, it kind of encourages people into these arm races where people say that the GPL has failed in its job because some companies don't hate it (again, the point of the GPL is not to be impossible for companies to use). BSL on the other hand is very straightforward, and because it's upfront about its goals, it's not subject to the same kinds of weird arm races and escalations. You release software as proprietary, we all recognize that it's proprietary and that you want compensation for it, and then at some point it becomes Open Source. That's a really simple model to think about and build around.
----
But all that being said, code that is licensed under the GPL is Open Source, period, regardless of what other licenses it is simultaneously offered under.
BSL licensed code before it expires is not Open Source or FOSS: it's proprietary code that later is Open Sourced once a certain amount of commercial value has been extracted from it.
Or is the problem that Elastic can't effectively monopolize that technology which they purposely offered to the world for free? Well, of course not... how can both of those be true at the same time? The choice to release a product as open source is to intentionally prevent it from being monopolized.
I think they are saying that when you tell people something is acceptable, then they can only assume it actually is acceptable to you.
I think that is false. Most things that are said assume that the listener will self-moderate. If I have Crohn's or IBS and I post a sign on my front-lawn saying "bathroom free to use for those in need" I'm not expecting you to pull up a tour-bus full of tourists, move into it and use it as housing, or a sex den for turning tricks. I mean, I should clarify my sign, but honestly if you don't meet me half-way with self-moderation, you are the reason we can't have nice things.
Above all, make sure you always leave money on the table, _especially_ if you are the bigger party.
I think this can become a complicated game of accounting though. Did Amazon take more than they need or did they just build a useful cloud service on top of a widespread open and free product that was released intentionally under those terms?
When Elastic chose the Apache license, what was the goal? Was it to allow as many people to benefit from the software as possible? If so, Amazon is clearly advancing that goal, not hindering it.
Or is the idea that Amazon is somehow blocking Elastic from competing in the cloud search space? Elastic is growing quite rapidly and Amazon's use of ES seems to have only accelerated that growth, so I don't really buy that either.
Furthermore consider this: Is Elastic reciprocating the generosity offered by Apache and the Lucene project, to which they basically did the same thing that Amazon did to them?
But you should expecting that, you can't assume the listener will self-moderate.
People are so diverse, I can't assume everybody behave the same, let alone behave the way I want.
Most free/open source software licences come from a different time. In most cases they are applied because the authors want to do open source and it's expected that the licence is enough to uphold that spirit. But it's not enough and hasn't been for a long time now. The AGPL was created for this reason but oddly developers have gone the opposite direction and "permissive" licences have become the fashion. Many of them are now realising there was a reason for licences like GPL and AGPL after all.
Apache 2.0, section 6:
> 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
Hence the license change yes?
Imagine putting a sign on your lawn that says people can walk on your lawn and are even allowed to poop on it if they feel like it and then getting mad at them when they do so.
That being said, I support their right to change their license to whatever they like if it helps them survive as a business or for whatever reason they see fit obviously, more power to them.