Marc Pichler

Looks like a few more folks were missing, I sent the remaining invites @open-telemetry/javascript-contrib-triagers | Owner | Status | Components | |-|-|-| | @psx95 | ✅ invite sent | resource-detector-gcp...

> Hi, so sorry I have somehow completely missed this issue for such a long time. I see my name is mentioned multiple times, but I'm not 100% sure what...

> Membership request completed: [open-telemetry/community#3088](https://github.com/open-telemetry/community/issues/3088) Thanks, invite sent!

> I think I am already part of this organisation? Happy to accept my duties for the typeorm repo Yes 🙂 Now you're also member of `@open-telemetry/javascript-contrib-triagers`. All sorted, thanks!...

Thanks @henrinormak - invite sent :) Looks like this issue is done. Thanks everyone 🙂

> I don't have concrete figures right now, but I'm wondering if creating delegation for every `Instrument` instance may increase performance implications. #3267 introduces a hook for instrumentation to update...

Hi, thanks for your interest in contributing to OTel JS. In order to add this feature, we need to ensure that it is safe for everyone to use before we...

We may also be able to convert uses of `Span` to `ReadableSpan` wherever interfaces expect a `ReadableSpan` instead of an actual SDK span.

> - it should be no problem to leave usage of new Span in sdk-trace-base tests right? > - should sdk-trace-base export the Span interface from @opentelemetry/api rather than the...

Yep, I agree we should document this better. Plenty of people run into this and it can be very frustrating.