Need Elastic licenses removed

[jordanoliver23]

Describe the bug

It looks there are some libraries with elastic as the license owner still. For example this one: https://github.com/opensearch-project/OpenSearch-Dashboards/blob/1.1/src/plugins/opensearch_dashboards_react/public/code_editor/.storybook/main.js.

If this is stated as the license for a particular library then we can't build a managed service that leverages this library. It looks like just an issue in cleaning them up but we would be out of compliance if we distribute libraries with this license.

Expected behavior
The correct attribution for each library.

OpenSearch Version
Please list the version of OpenSearch being used.
1.0

Additional context
I don't know a way of easily query for attribution. I'd love some suggestions if you have any.

Copied from #1129:
It looks like this file was missed by the license header sweep in #259. The license header should be updated to reflect the correct licensing.

The default config that both of these files export is under the Apache 2.0 license: https://github.com/elastic/kibana/blob/v7.10.2/packages/kbn-storybook/lib/default_config.ts

Files:

• https://github.com/opensearch-project/OpenSearch-Dashboards/blob/main/src/plugins/opensearch_dashboards_react/public/code_editor/.storybook/main.js
• https://github.com/opensearch-project/OpenSearch-Dashboards/blob/main/src/plugins/embeddable/.storybook/main.js

[jordanoliver23]

thank you. @tmarkley , is there any other mentions of this license in the repo now? Meaning did your scan also do another pass across the entire repo?

[tmarkley]

@jordanoliver23 yes, in my PR I removed the Elastic License as an allowed license header from the linter so the build will fail if any files use that header. I also did a manual search and didn't find any other instances.

[jordanoliver23]

@tmarkley , just wanted to confirm something. Did you remove the library or attribute another license to the library? I wouldn't be allowed to just remove the license file only.

[tmarkley]

@jordanoliver23 I attributed the correct Apache 2.0 license to both of the offending files. The Elastic License isn't attributed anywhere now.

[jordanoliver23]

Our legal org asked me to follow up with the following question: How did you determine Apache is the correct license? According to https://github.com/elastic/kibana/blob/v7.10.2/src/plugins/embeddable/.storybook/main.js, the correct license is Elastic License Agreement only. Did Elastic agree to relicense it?

[tmarkley]

No, there hasn't been an agreement for that, but the history seems very odd to me. Looking at the commits, these two files were moved from x-pack to the main repo plugin directory, but the license header was not changed. Both of these files merely export a default configuration (which is/was Apache 2.0 code), so it's not clear why the license wouldn't reflect Apache 2.0 at the time just as the rest of the non-x-pack code did.

@hyandell is there a process that we need to go through for this?