Carlos Alberto Cortez

Overall good, only a minor non-blocking comment: > PRs submitted to address the issue prior to a sponsor volunteering should be rejected. I've seen this a lot for small corrections...

> if trace id is randomly generated (most if not all SDKs) set the random flag I wonder if we should strongly suggest all SIGs _do_ generate random ids (if...

I have a draft PR on how this could be supported: https://github.com/carlosalberto/opentelemetry-collector-contrib/pull/2 Please provide feedback on whether this is a feasible approach ;) @codeboten

The TC briefly discussed this last week - overall, the _existing_ solution to this 'problem' was deemed as a good one. It was recommended that, if anything breaks a vendor,...

Hey, just a FYI: As we iterate (hopefully fast) on this issue, we will prepare to merge https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1411 and https://github.com/open-telemetry/opentelemetry-python-contrib/pull/1657 - as this two incorporate the _current_ Specification & Semantic...

I did a quick pass on the requirements, and it indeed looks we are fine, but out of curiosity, has the Security SIG done a full review?

We are missing the Messaging SIG, which is currently incorporating the latest OTEP into the Spec, and we definitely want to have our "1.0" this year, with myself being the...

+1 for "Public meeting".

@trask done ;)

Correct, unrelated to auto-instrumentation. Will update the title.