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 [email protected] 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.