Comment by ddevault

I'm happy to see a couple of good choices made here:

- Sticking with Apache 2.0

- Asking for a Developer Certificate-of-Origin rather than a copyright assignment

This bodes well for the future of this fork. Amazon also has the resources necessary to keep up consistent and quality maintenance of a project on this scale.

Elastic would definitely like you to view AWS as the Big Bad here, but their response to the Elastic betrayal is very good, and I would like to see more like this in the future.