Leighton Chen

@dpgrodriguez Yes there is nothing in the queue because the Worker that fills them up doesn't exist.

@arnabbiswas1 I am not too familiar with jobib but it seems like the worker fork behaviour is similar to the other multiprocessing libraries. As of today there is not a...

You are correct, there is no urllib3 support currently.

Has there been any discussion on how to handle instrumenting more than once to avoid duplicate telemetry? In [Python](https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/opentelemetry-instrumentation/src/opentelemetry/instrumentation/instrumentor.py#L46) we simply utilize a property on the base class that all...

Does this not apply to [logs](https://github.com/bogdandrutu/opentelemetry-specification/blob/3e9c4d081464399190456feaf14933da022cbc1f/specification/logs/api.md#get-a-logger) as well? Also the scope attributes should not be part of tracer identity either right?

@RangelReale Please pull from the latest main branch to fix the failing contrib tests. Also please fix the lint/spellcheck so we can get this merged.

@ocelotl Why skip changelog? I think renames should be included as part of it. We already include logging related entries in the changelog despite it being experimental.

@ocelotl I'm not following your suggestion here. Are you proposing to release a new differently named package per semantic convention version? i.e. `opentelemetry-semantic-conventions-1.12` for v1.12 of semantic conventions and also...

@ocelotl 1. How does that solve the original goal of being able to mark semantic conventions package stable? 2. How does this make it so that we don't have to...

@ocelotl > There is another solution that has all the advantages of the approach I suggest without this problem, and that is to make a new package named opentelemetry-semantic-conventions-... with...