Marc Pichler

@AbhiPrasad thanks for working on the fix, would you mind if I assign you? :slightly_smiling_face:

I think that this behavior is intentional. AFAIK in this context only http spans are supposed to be `SpanKind.SERVER` (these are generated by `@opentelemetry/instrumentation-http`). The extra spans generated by `@opentelemetry/instrumentation-express`,...

I believe this may be an issue that's better suited for the Azure SDK repo :thinking: It's seems related to the mapping of OTel to Azure Monitor, which is out...

> @pichlermarc Looking for approval. Also wondering if you are fine with moving this sampler out of /incubator? @jj22ee I'd rather have it remain in incubating for now since the...

> @pichlermarc Moved the Sampler back into incubator, also updated to SDK 2.0. @jj22ee thanks! There also seem to be some changes to the top-level `package-lock.json` from a previous commit...

> Nice! When will this be released on NPM? Just asking, because I noticed that #5079 was not released yet, only merged. Not sure what the current state is. We'll...

Yep, what @schiemon said is the correct reason. It's not allowed by the spec at the moment so we also don't allow it.

Opened #2641 to address the first point ("Add expectations for js-contrib-triager role")

Alright, this is step 2 "Confirm current [codeowners](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/.github/component_owners.yml) are members of OTel org" I took a look at the current component-owners, and it looks like the following users are not...

Alright I sent out the invites to everyone who's currently on the owners list - I left out current maintainers as they are already assigned to @open-telemetry/javascript-contrib-triagers due to being...