Trask Stalnaker

> > Tracing doesn't, but IIRC correctly there's a reason for that 🤔 that we've previously discussed. > > maybe to keep trace context propagation enabled even if no (local)...

@jeromeinsf could you help us find someone from AWS that could review this PR?

> * `opentelemetry-extension-aws` - Not sure what the history is here, but xray propagator isn't included in the [list of propagators](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/context/api-propagators.md#propagators-distribution) defined the spec and including it in the core...

Should micrometer shim be moved out? And settle on criteria for core repo: spec'd (or on its way to spec'd) AND not semantic convention related

My preference would be to move "bridges to other telemetry libraries" to the contrib repository, where experts in the target libraries can be component owners for them.

We could probably reverse the dependency between instrumentation and contrib repos, making instrumentation repo depend on contrib repo. We have already discussed moving runtime attach and static instrumenter to the...

> Due to the presence of a growing number of library instrumentation artifacts, I've been viewing the instrumentation repo as a general home for instrumentation This is correct, and has...

Here's a proposal based on the above: * Publish an `opentelemetry-javaagent-contrib-{version}.jar` from the contrib repository * Keep the current repo dependencies: > `opentelemetry-java` > `opentelemetry-java-instrumentation` > `opentelemetry-java-contrib` * Use @jack-berg's...

> * What to do with [opentelemetry-extension-noop-api](https://github.com/open-telemetry/opentelemetry-java/blob/main/extensions/noop-api). We [like](https://github.com/open-telemetry/opentelemetry-java/issues/4661#issuecomment-1207073120) the idea of moving it to `opentelemetry-extension-incubator`, but after some research that's not actually a good idea. The problem is it...

I've kicked off the discussion in the instrumentation repo https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/6245, and added the topic of naming to the SIG agenda for tomorrow. Once we close on naming, I'll do the...