legal: remove licenses of dependencies #137
Conversation
Align with other Open Telemetry projects and remove the licenses text from dependencies from this project. Also remove vendor specific tooling to manage these third party licenses. Signed-off-by: Florian Lehner <florian.lehner@elastic.co>
There was a problem hiding this comment.
AFAIK we still need to abide by the CNCF allowed 3rd party license policy. I'm not sure about the licenses themselves (e.g. look at https://github.com/open-telemetry/opentelemetry-go-instrumentation/LICENSES/) so maybe we should ask for clarification, but if we remove the tooling aren't we making the process of determining compliance with the CNCF policy harder?
Yes - this is without question. Following the CNCF policy for allowed 3rd party licenses should continue without change. With open-telemetry/community#2294 I have opened a request for guidance. At the moment the majority of OTel repositories does not store and provide the licence text for dependencies, like this project. Depending on the responce in open-telemetry/community#2294, either 3rd party licenses should not be stores within a repository, then this proposed change should be merged, OR the process to update the license files for 3rd party licenses should be automated - to avoid manual changes like #135. |
Align with other Open Telemetry projects and remove the license texts of dependencies from this project.
Also remove vendor specific tooling to manage these third party licenses.