122

Elasticsearch is Open Source, Again (www.elastic.co)

submitted 2 weeks ago* (last edited 2 weeks ago) by geneva_convenience@lemmy.ml to c/opensource@lemmy.ml

24 comments fedilink hide all child comments

[D.N.A] Elasticsearch and Kibana can be called Open Source again. It is hard to express how happy this statement makes me. Literally jumping up and down with excitement here. All of us at Elastic are. Open source is in my DNA. It is in Elastic DNA. Being able to call Elasticsearch Open Source again is pure joy.

[LOVE.] The tl;dr is that we will be adding AGPL as another license option next to ELv2 and SSPL in the coming weeks. We never stopped believing and behaving like an open source community after we changed the license. But being able to use the term Open Source, by using AGPL, an OSI approved license, removes any questions, or fud, people might have.

[Not Like Us] We never stopped believing in Open Source at Elastic. I never stopped believing in Open Source. I’m going on 25 years and counting as a true believer. So why the change 3 years ago? We had issues with AWS and the market confusion their offering was causing. So after trying all the other options we could think of, we changed the license, knowing it would result in a fork of Elasticsearch with a different name and a different trajectory. It’s a long story.

you are viewing a single comment's thread
view the rest of the comments

[-] velox_vulnus@lemmy.ml 23 points 2 weeks ago* (last edited 2 weeks ago)

What a deceptive, and contradictory statement to make, kek. The SSPL is AGPLv3 with Section 13 modified. The net-difference is just one section between personal and commercial use.

The SSPL is based on the GNU Affero General Public License (AGPL), with a modified Section 13 that requires that those making SSPL-licensed software available to third-parties (modified or not) as part of a "service" must release the source code for the entirety of the service, including without limitation all "management software, user interfaces, application program interfaces, automation software, monitoring software, backup software, storage software and hosting software, all such that a user could run an instance of the service using the Service Source Code you make available", under the SSPL. The chapter structure of the Server Side Public License is identical to that to the AGPL, except that the GPL preamble and application instructions are stripped from the license text.

And meanwhile, have a look at the Elastic License 2.0:

The Elastic License 2.0 applies to our distribution and the source code of all of the free and paid features of Elasticsearch and Kibana. Our goal with ELv2 is to be as permissive as possible, while protecting against abuse. The license allows the free right to use, modify, create derivative works, and redistribute, with three simple limitations:

You may not provide the products to others as a managed service

You may not circumvent the license key functionality or remove/obscure features protected by license keys

You may not remove or obscure any licensing, copyright, or other notices

We tried to minimize the limitations just to those that protect our products and brand from abuse.

You can keep lying to yourself, Shay Banon.

[-] fmstrat@lemmy.nowsci.com 3 points 2 weeks ago

I think you are confused. You can use ELK under AGPL with this news going forward. The fact that they have to retain SSPL, too, because of previous contributors under that license, has nothing to do with the fact that you can use AGPL going forward. I've read your other responses,but they all seem to go down the same seemingly incorrect direction.

Am I missing something?

load more comments (14 replies)

this post was submitted on 30 Aug 2024

122 points (94.9% liked)