Provide necessary license and documentation for envoy Jaeger tracing plugin to ensure open source designation

[cjp421]

Title: Provide necessary license and documentation for envoy Jaeger tracing plugin to ensure open source designation

Description:

I would like to leverage the Jaeger Tracing plugin within my organization's envoy docker containers. In order for this to be allowed, I need to provide evidence that the plugin uses a support license agreement. I have submitted envoyproxy/misc#1 requesting for a license to be specified and the README updated to provide a reference to the source code used to generate the plugin.

Relevant Links:

Related conversation - jaegertracing/jaeger-client-cpp#183 (comment)
Reference to plugin in envoy examples: https://github.com/envoyproxy/envoy/blob/main/examples/jaeger-native-tracing/Dockerfile-frontenvoy#L14-L17

[alyssawilk]

cc @htuch @phlax

[phlax]

cc @lizan

[cjp421]

Any updates on this?

[phlax]

not sure what the license situation is exactly - i added (or maybe updated) the binary to fix an issue with abi incompatibility some time ago

the binary i added was iirc from a tetrate recipe, i think @lizan knows more about where it came from originally - the url has since been shifted to within the envoyproxy namespace, so i assume its Apache licensed - but not sure and not sure where the source/compile recipe is etc

ideally with this we add some bazel build to build this plugin in envoys ci and then we wont have to worry about this so much or the other concerns iwith hosting a binary in the repo

[cjp421]

@lizan can you provide any insights into the licensing around the jaeger plugin for envoy? Would it be possible to get the changes you made committed to github with the relevant LICENSE file? Or possibly add a LICENSE file to the envoyproxy/misc repository?

[lizan]

Yes it is Apache license. the Jaeger opentracing C++ library is already deprecated so I don't think we want to invest more in this.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.