-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Elastic.co, AWS OpenDistro, and Olivere #1466
Comments
Related to #1240 |
Hi C.J. My personal view on this is that this library should benefit the community. To best serve the community, my goals for this library are 1) to be stable, 2) to limit the amount of breaking changes during minor versions, and 3) work on as many Elasticsearch versions and distros as possible. My take on the future of this library is written down in #1240. I'd like to apologize for currently not being very active in working on this library. Day-time work related issues are more important to me right now. I see quite a number of very useful contributions in the form of PRs, but on the other hand I've not seen too many things that actively prevent people from using the library. Having said that, I really hope to pour in some days and work on the queue of PRs and issues that's already there, and even add some more stuff that I have on my list. |
Awesome! I like the vision, and good to know that the corporate machinations aren't really shaking you. And major props for this repo overall, it's a shining example I like telling my friends about. |
Where do folks stand amid the upcoming changes to the Elastic.co license, and expansion of AWS's Open Distro ?
Beyond Elastic.co v7.10 (after the license changes) , can and will
olivere/elastic
continue to work with new versions?What if olivere/elastic became part of the AWS OpenDistro umbrella? Would that give this repo more love and resources for keeping it maintained? Or would that add headache?
The text was updated successfully, but these errors were encountered: