Is this repository AWS affiliated plugins locked from merging new features?

[ithompson-gp]

General discussion... I've noticed PR addressing concerns with regard issues with AWS Lambda/SDK instrumentation that are unassigned or un-triaged or been in review for some time now.

Wondering if us users of these libraries should disengage from this community and OTEL going forward?

(example PR (addressing lambda instrumentation not following conventions): https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1411)

Other examples:

• https://github.com/open-telemetry/opentelemetry-js-contrib/issues/999
• https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1922
• https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1813
• https://github.com/open-telemetry/opentelemetry-js-contrib/issues/1528
• https://github.com/open-telemetry/opentelemetry-js-contrib/issues/1509
• https://github.com/open-telemetry/opentelemetry-js-contrib/issues/707

[trentm]

Adding some of my understanding:

• I closed #1813 just now. A separate fix went in for that one.
• I closed #1509 just now. I think a fix went in for that a long while back, but the issue wasn't closed at the time.
• The Lambda-related one(s) were delayed, at least partially, because there was a lot of discussion, churn, and change at the spec level for what to do here. I'm not following the FaaS discussions closely, but I think the spec has settled on how to handle trace-context propagation in Lambda. This was discussed last week in the OTel JS SIG.
• For #707, there was some more recent discussion in a separate issue. I added a note to #707 -- which I should have done before. This is a harder case, at least from my point of view, because I'm advocating removing a current feature.

• 1528 does indeed look like it is stalled. Adding a separately reproducible example would help.