Back to opensource license too?

[ronnyek]

This is more of a general question, and prompted by recent announcement that elastic search was going "back to opensource".

I'm wondering if this library will be at all affected by that announcement. Currently, the license seems to still read as if it was the proprietary license that may or may not have limitations for usage.

With the licensing that elasticsearch had (agpl / elastic license), nothing elastic related would be remotely considered for usage in our applications etc.

Does the "back to opensource" initiative (for elastic search and kibana) have implications here as well? If so would it be possible to get a better understanding of what license elasticui would have, and what the limitations would be?

Thanks

[smith558]

Very interested in this as well.

[alessandrotesoro]

I'm interested in this too. I sent an email to elastic_license@elastic.co on the day of the announcement but received no reply.

[linghengqian]

• According to Adds AGPL 3.0 license #8012 (comment) , it looks like the LICENSE will not be changed.

• For elasticsearch and kibana, the license changes so far only affect the source code, and I haven't seen any further product changes. I haven't seen anyone distribute agpl-3.0-only binaries or docker images by manually compiling. And finally, since the docker image uses Linux, gpl v2 is always present.

[stil]

Any official statement on future licensing of this library? The closed PR didn't mention whether OSS is coming later or not coming at all.

[JasonStoltz]

Sorry for the delay.

We had a quick conversation about whether nor to move this to the new licensing model or not. The short answer is that we're not going to do it now, but we would consider it for the future if there is enough demand or a compelling reason to do so.

Traditionally, EUI has followed the licensing of Kibana. So if we were to make the move, our licensing would simply change to be the same as Kibana. There would be no product changes, it would just add the additional AGPL license.

I am not well-versed enough about the topic to speak about details regarding the license itself. And in fact, part of the reason to not change licensing at this point was to simply avoid any confusion.

For reference, here is the blog post with the announcement where you can likely find more information.

[JasonStoltz]

I'll leave this issue open for the time being in case folks have thoughts or feedback.

[cee-chen]

@JasonStoltz Should we go ahead and convert this into a discussion instead of an issue?

[ronnyek]

What would the purpose of that be? Sounds like the answer was a no, so I'll just blacklist this on my package server at work and walk away from elastic.

Adios!

[JasonStoltz]

Hey @ronnyek. Can you help me understand your concern? Kibana itself is now open source, I had assumed EUI wouldn't necessarily need the same open source licensing, but again, if this is causing an issue we can certainly reconsider.

[smith558]

Hey @ronnyek. Can you help me understand your concern? Kibana itself is now open source, I had assumed EUI wouldn't necessarily need the same open source licensing, but again, if this is causing an issue we can certainly reconsider.

I think the issue for most people (definitely myself) is that we would like to be able to use EUI for projects completely unrelated to Kibana and/or Elasticsearch, as was previously possible. However, this may not be possible anymore (please correct me if I am wrong).