Tigran Najaryan

@jpkrohling can you tell more about the bare-metal boxes you said may be available? How many there, who owns them, etc.

It is probably useful to have some preliminary thoughts on these before starting the actual implementation: - Who is going to be responsible for the ongoing maintenance? Is the answer...

@jmacd @MrAlias just to confirm: there will not be exemplars support in the GA based on how this is labeled, correct?

cc @bogdandrutu @MrAlias

> 1. It raises the concern of security response in OTel -- clearly, a [SECURITY.md](https://github.com/open-telemetry/.github/blob/main/SECURITY.md) exists, but what is the response? For example, [Kubernetes](https://kubernetes.io/docs/reference/issues-security/security/#security-vulnerability-response)) The vulnerabilities reported to cncf-opentelemetry-tc are...

>Instead, what we currently have is that applications have to install vendor-specific exporters which means that if you don't control the source code for an application, you're basically left without...

I agree with you. We should recommend OTLP on all hops, with or without Collector, and at the vendors' ingest endpoints. As an example I think we need to highlight...

I am not sure about the "who removed" part, but I think the policy currently says that maintainers do not normally have admin permissions: https://github.com/open-telemetry/community/blob/main/docs/how-to-configure-new-repository.md#permissions I think this was also...

Here, found the discussion: https://github.com/open-telemetry/community/issues/616

Yes, that should work. What sort of Dart support do you expect from this repository? This repository merely contains proto file definitions which are language independent.