News for hackers. Stuff that matters.
Re:AWS announces forks of Elasticsearch and Kibana by fastball on Thursday January 21, 2021 @06:13PM (#25865931)
Then Elastic should've come up with a non-Apache-2.0 license at inception.

Licenses exist for a reason. The onus is on the person choosing the license to choose one which aligns with their intentions. You cannot and should not expect downstream consumers of the software to confine themselves to some subset of the actual license's allowed activities just because it's the "nice" thing to do (as of course this assumes morality is in any way objective).

Re:AWS announces forks of Elasticsearch and Kibana by dodobirdlord on Thursday January 21, 2021 @07:41PM (#25866774)
They made a mistake with their original licensing, and now they have corrected it. The comments on this post seem strangely invested in Elastic not fixing their mistake.
Re:AWS announces forks of Elasticsearch and Kibana by neop1x on Saturday January 23, 2021 @07:24AM (#25881725)
Did they made a mistake? It looks to me that they took advantage of Splunk being proprietary. Not many people would use closed Splunk alternative. So they have made an open alternative and everyone loved it and this is what created the community and made them popular. Then they started using their position to force people into their proprietary Basic package because there was no security in the OSS version. That caused many data leaks from unsecured Elastic clusters. Can you imagine MariaDB not having any security by default? Or nginx without ACL? I never cared about Machine Learning, APM, SIEM and their other "products". Then they released "basic security" which was not open and was still pretty limited (e.g. not supporting OpenID). Elastic is big now, listed on the stock exchange so I understand they have to listen to their shareholders. While I don't like Amazon business and I am not their customer, I actually welcome this attempt to finally make a basic usable Elastic really open!
Re:AWS announces forks of Elasticsearch and Kibana by fastball on Friday January 22, 2021 @12:22AM (#25868602)
Right but "who is wrong" is what the disagreement is about, and if Elastic made the mistake then arguably it is them who are wrong.

In contrast, a number of people here are acting as if AWS is totally in the wrong. But the only wrong here is Elastic making the mistake and then acting as if the whole thing is AWS' fault. No, if you license your software improperly that's on you, not anyone else.

Re:AWS announces forks of Elasticsearch and Kibana by hrktb on Friday January 22, 2021 @02:09AM (#25869243)
Does it need to be a binary thing ?

Elastic made a strategic mistake, and Amazon made the jerk move that was open to them.

Re:AWS announces forks of Elasticsearch and Kibana by kevincox on Friday January 22, 2021 @08:09AM (#25871346)
What about Elastic making the "jerk move" by switching the license under Amazon?

Amazon built the product with the hope that it would continue to be developed with that license. What are they supposed to do with the license change? Just accept whatever Elastic said? I don't think you can blame them for taking the last version where they agreed with the license and continue to use and develop it. Sure, maybe making it open is a bit of a jab back, but even in isolation it makes sense for them.

Re:AWS announces forks of Elasticsearch and Kibana by Xylakant on Friday January 22, 2021 @11:29AM (#25873061)
> What about Elastic making the "jerk move" by switching the license under Amazon?

They’re also switching out the license under everyone else. It’s maybe notable that elastics cloud offering was acquired at some point (it used to be found.io). I used to do elasticsearch consulting and I could name a few customers that will now have to reevaluate their product.

Re:AWS announces forks of Elasticsearch and Kibana by eloisant on Friday January 22, 2021 @05:51AM (#25870501)
I don't see how AWS is being a jerk.

They're a hosting company, they're hosting open source software and they're doing it well.

Re:AWS announces forks of Elasticsearch and Kibana by hanniabu on Thursday January 21, 2021 @07:17PM (#25866599)
What open source license would prevent someone from capitalizing on your project?
Re:AWS announces forks of Elasticsearch and Kibana by Phrodo_00 on Thursday January 21, 2021 @11:29PM (#25868329)
No open source license prevents people from capitalizing your project. Adding a non-commercial clause to an OSS license makes it not comply with OSS anymore.

Preventing companies from hosting the software with propietary changes can be done with licenses like the AGPL, but again, the objective is not to disallow commercial use, but rather to force the source code to be available for the users of the software.

Re:AWS announces forks of Elasticsearch and Kibana by fastball on Friday January 22, 2021 @12:24AM (#25868615)
None. That's... kinda the point of OSS.
Re:AWS announces forks of Elasticsearch and Kibana by __blockcipher__ on Thursday January 21, 2021 @06:20PM (#25866026)
And frankly, I don't even buy the morality argument. It is a moral good to provide value to customers such that they voluntarily choose to give you money in exchange for that value.

These people have this bizarre fusion of capitalist and communist reasoning, I really can't reconcile it. On the one hand they seem to think profit is fundamentally evil, but on the other hand they seem to think the problem is that Elastic isn't being allowed to monopolize all the profit.

Well, which is it? Did Elastic release non-restrictively-licensed free software out of the goodness of their hearts, giving it away with no expectation of a return? Or did they create this codebase purely for profit, and thus have no claim to moral highground? It's all so silly and childish.

And the biggest irony is, Elastic is already a successful business. They're trying to pretend their business model is not viable as long as Amazon keeps operating, which is just gaslighting.