Page MenuHomePhabricator

Elasticsearch, a CirrusSearch dependency, is switching to SSPL/Custom licence
Open, Needs TriagePublic

Description

According to their blogpost (https://www.elastic.co/blog/licensing-change):

Starting with the upcoming Elastic 7.11 release, we will be moving the Apache 2.0-licensed code of Elasticsearch and Kibana to be dual licensed under SSPL and the Elastic License, giving users the choice of which license to apply.

Their FAQ on 2021 License Change : https://www.elastic.co/pricing/faq/licensing

Considering this is happening:

  1. WIll CirrusSearch rely on ElasticSearch in the near future (say on version 7.x)?
  2. Will CirrusSearch rely on ElasticSearch in long-term?
  3. According to task T213996, the switch from MongoDB had happened because it was removed in Debian and therefore will be unsuitable for long-term use., and therefore it was unclear if a precedent was achieved. Are there any policy change or clarification if another dependency announced to switch to a license that may not be suitable for MediaWiki?

Context on proprietary relicensing:
https://sfconservancy.org/blog/2020/jan/06/copyleft-equality/

Existing alternative venues:
https://opendistro.github.io/for-elasticsearch/contribute.html ("distribution" or "fork" depending who you ask, no CLA)

Some announced forks:
https://aws.amazon.com/blogs/opensource/stepping-up-for-a-truly-open-source-elasticsearch/
https://logz.io/blog/open-source-elasticsearch-doubling-down/

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Gacelperfinian renamed this task from Elasticsearch will switch to SSPL to Elasticsearch, a CirrusSearch dependency, is switching to SSPL/Custom licence.Jan 15 2021, 1:22 AM

WIll CirrusSearch rely on ElasticSearch in the near future (say on version 7.x)?

Yes. CirrusSearch is currently on 6.5.4. It will likely upgrade to 6.8.x soon. These versions are EOL and stopped receiving security updates from elastic in Nov 2020.

Will CirrusSearch rely on ElasticSearch in long-term?

Yes? No? Maybe? It will take months to figure this out.

According to task T213996, the switch from MongoDB had happened because it was removed in Debian and therefore will be unsuitable for long-term use., and therefore it was unclear if a precedent was achieved. Are there any policy change or clarification if another dependency announced to switch to a license that may not be suitable for MediaWiki?

The rule of thumb, it may or may not be a strict rule somewhere, is that WMF deploy's software with OSI approved licenses. There is at least some mention under development policys that new services must be licensed under an OSI-approved license.

Also for notetaking: Kibana will also be affected by this change, but I am not sure if WMF stack uses Kibana in some way (if there is any, this should be on another task anyways).

The Translate extension also uses ElasticSearch.

Nemo_bis renamed this task from Elasticsearch, a CirrusSearch dependency, is switching to SSPL/Custom licence to Elasticsearch is going proprietary with a SSPL/custom licence; forks coming.Jan 24 2021, 4:47 PM

This isn't the task for the Logstash or Translate issues. Please see T272238: Elasticsearch and Kibana are switching to non-OSI-approved SSPL licence for the former and create a new task for the latter, as implied above.

Jdforrester-WMF renamed this task from Elasticsearch is going proprietary with a SSPL/custom licence; forks coming to Elasticsearch, a CirrusSearch dependency, is switching to SSPL/Custom licence.Jan 24 2021, 6:11 PM
Gehel claimed this task.
Gehel subscribed.

For the moment, we're staying on Elasticsearch 7.x (once we've migrated from 6.x to 7.x), but we're blocked on upgrading past 7.10.2 because of licensing. There is a larger question of what exactly are the needs in term of Search that needs to be resolved.

There isn't a clear acceptance criteria on this task, so closing it for now. Feel free to re-open as needed.

Legoktm subscribed.

For the moment, we're staying on Elasticsearch 7.x (once we've migrated from 6.x to 7.x), but we're blocked on upgrading past 7.10.2 because of licensing. There is a larger question of what exactly are the needs in term of Search that needs to be resolved.

There isn't a clear acceptance criteria on this task, so closing it for now. Feel free to re-open as needed.

I don't think staying on Elasticsearch 7.x is a long-term solution, is it? I think we can consider this ticket resolved once CirrusSearch has moved to using something that is properly open source under an OSI license.

@Legoktm, see T272238 and T280482 - it seems OpenSearch is the relevant replacement in the future, and this task can be left closed.

Gehel removed Gehel as the assignee of this task.Apr 15 2024, 2:00 PM