Skip to content
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

Closed
tfarrep opened this issue Aug 7, 2022 · 5 comments
Closed

Investigate license status of generated code #73

tfarrep opened this issue Aug 7, 2022 · 5 comments
Assignees
Labels
enhancement New feature or request

Comments

@tfarrep
Copy link
Contributor

tfarrep commented Aug 7, 2022

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)

@Yury-Fridlyand
Copy link
Collaborator

The generator wasn't used yet after migration to OpenSearch.

@dblock dblock self-assigned this Aug 8, 2022
@dblock
Copy link
Member

dblock commented Aug 8, 2022

I'm taking this and will seek guidance accordingly.

@Yury-Fridlyand Yury-Fridlyand added the enhancement New feature or request label Aug 11, 2022
@dblock
Copy link
Member

dblock commented Aug 15, 2022

I'm taking this and will seek guidance accordingly.

Still navigating non-technical folks ;)

@dblock
Copy link
Member

dblock commented May 1, 2023

The general guidance is that we have to keep the license if the generator injects code under ES copyright. What does the generator inject?

@dblock
Copy link
Member

dblock commented Sep 30, 2023

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.

@dblock dblock closed this as completed Sep 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants