-
Notifications
You must be signed in to change notification settings - Fork 49
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
Investigate license status of generated code #73
Comments
The generator wasn't used yet after migration to OpenSearch. |
I'm taking this and will seek guidance accordingly. |
Still navigating non-technical folks ;) |
The general guidance is that we have to keep the license if the generator injects code under ES copyright. What does the generator inject? |
The official answer is: We need to treat this as forked code. We would need to keep the Apache header (could be the standard "SPDX-License-Identifier" one, not the auto-generated one), with Elastic's copyright notice on it. Once we make additions, we can add our copyright as well, but keep Elastic's too. Closing this, let's stick to the guideline below. |
I'm curious about what legal situation the generated API code is in, as the template outputs the elasticsearch licensing: https://github.com/opensearch-project/opensearch-net/blob/1.0.0/src/ApiGenerator/Views/GeneratorNotice.cshtml#L3-L28
If it's generated does it need to remain licensed to ES? Is the status of the generated code tied to the status of the generator itself?
Potentially a weird situation if some future API endpoint is entirely unique to OS, but all generated code includes licensing to ES?
Originally posted by @tfarrep in #69 (comment)
The text was updated successfully, but these errors were encountered: