Where does Elastic claim SSPL is open source?
Licensing changes to Elasticsearch and Kibana
81–90 of 378 posts
Re: Licensing changes to Elasticsearch and Kibana
#82This is an alarmist headline. The SSPL license to which they are switching only requires your code to be open sourced if you are providing Elasticsearch itself as a service. This change is directed at cloud providers who take open source software and then provide them as a service for payment without contributing to the project. If you are using Elasticsearch on your backend to build search-enabled products or websites, then this does not apply to you.
Edit: Not a lawyer!
Re: Licensing changes to Elasticsearch and Kibana
#83How does this affect people providing “search” functionality of arbitrary items, but not Elasticsearch itself (AWS)? Where is the line drawn? Is the SSPL vague enough for that?
Re: Licensing changes to Elasticsearch and Kibana
#84It's just a change to make sure that those who resell ES as a service share their code.
We use AWS's ES. And, as far as I'm concerned they already open-source their version.
SSPL is actually helping the open-source community here
Re: Licensing changes to Elasticsearch and Kibana
#85Where does Elastic claim SSPL is open source?
"open source" appears 19 times, but they very very carefully weasel-word their way away from saying they are still open source. but wow how close they come, how much it seems to imply they still are going to be open source. some examples:
> SSPL is a source-available license created by MongoDB to embody the principles of open source while providing protection against public cloud providers offering open source products as a service without contributing back.
forgive me for not immediately seeing that this is an "open source inspired" license, not open source.
> As previously mentioned, over the last three years, the market has evolved and the community has come to appreciate that open source companies need to better protect their software in order to maintain a high level of investment and innovation.
...by no longer releasing open source software
> As previously mentioned, over the last three years, the market has evolved and the community has come to appreciate that open source companies need to better protect their software in order to maintain a high level of investment and innovation.
again, "we value the same principles as open source... but we're not going to be open source any more" obfuscation.
your doubt is unbecoming, bevacqua.
Re: Licensing changes to Elasticsearch and Kibana
#86Where does Elastic claim SSPL is open source?
The Elastic blog post announcing the change never says exactly those words, but it repeatedly talks about being an "open source company" with an "open source product" -- despite the fact that Elasticsearch is now available under a choice of two different licenses, neither of which is "open source" under any reasonable definition.
(The other option, the Elastic License, allows you to use the product in either source or binary form, but you may not make derivative works or compile your own binaries except for testing.)
Re: Licensing changes to Elasticsearch and Kibana
#87Where does Elastic claim SSPL is open source?
Also, why is SSPL not open source? As far as I can tell, it mostly just seems like the APGL, but taken to 11. I can definitely appreciate why it's a problematic license, but I don't think "not open source" is its problem.
Re: Licensing changes to Elasticsearch and Kibana
#88This is an alarmist headline. The SSPL license to which they are switching only requires your code to be open sourced if you are providing Elasticsearch itself as a service. This change is directed at cloud providers who take open source software and then provide them as a service for payment without contributing to the project. If you are using Elasticsearch on your backend to build search-enabled products or websit…
I think these are relevant from the Elastic blog post:
- no impact on the overwhelming majority of our user community
- no impact on our cloud customers or self-managed software customers
Also, this helped calm my nerves: https://www.elastic.co/pricing/faq/licensing
Re: Licensing changes to Elasticsearch and Kibana
#89> It can remain on version 7.10, but then it will no longer receive future updates
Does this mean anyone using version 7.10 or lower is not bound by SSPL license and Apache2 still applies?
Re: Licensing changes to Elasticsearch and Kibana
#90Just because cloud services make it basically impossible to get resources for your project doesn't mean you're allowed to actually do something about it. Apparently.