upvote
I'm not following why your users wanted Apache 2.0 - you wrote:

> Under Apache 2.0, every version we've released stays under those terms whatever we do later.

But isn't that true of all licenses? While you can relicense anything, doesn't a published/released codebase stay under the license its released with?

reply
The Elastic license is also somewhat hostile to community forks. In particular:

> You may not move, change, disable, or circumvent the license key functionality in the software, and you may not remove or obscure any functionality in the software that is protected by the license key.

So a fork would have to keep any code related to or protected by a license key, even if it is no longer possible to obtain a license key (say because the copyright owner went out of business).

One of the big advantages of using open source software is that you are much less dependent on continuity of service from the vendor. If the software maker goes out of business it is possible for the project to continue life in a fork made by a community or another business, foundation, etc. However, the limitations in the Elastic license make that less likely to happen, and limit what you can do with your own fork.

reply
For a bit more clarity, our users wanted full open source v. a more limited license like a business source license or elastic 2.0 license which had some restrictions, including not being able to host it as a service. In terms of licensing, there are examples of companies that have been open source and gone back to more restrictives licenses like Elastic, to protect themselves from hyperscalers hosting the software. Our position is that we're open source now and not going back.
reply
I think the implication is that any relicensing couldn't retroactively put the existing users under the new license and they could continue on with a fork like Valkey or OpenSearch.
reply
I was under the impression that there were scenarios in which licenses were revokable and that you're not necessarily allowed to waive that in the text of the license. If true though (obviously not a lawyer, and my memory is fuzzy on this point), it's definitely not been heavily tested in the courts.
reply
I love to see it, and though I remain a skeptic that it is viable long term, I hope it works out. Good luck!
reply
Well, that's definitely a risk :) and we want to be here long term. I guess we will see, but philosophically, we think people should own their own data and the intelligence around it, so we felt like open source was 100% the right path.
reply