Seeking maintainers for opentelemetry-aws, opentelemetry-datadog, opentelemetry-stackdriver — to be removed if unowned

[cijothomas]

The following three crates in this repo currently have no committed maintainer:

• opentelemetry-aws
• opentelemetry-datadog
• opentelemetry-stackdriver

These crates were originally part of the opentelemetry-rust main repo and were moved here when the contrib repo was created. They have not had clear ownership since.

As maintainers of OpenTelemetry Rust, we focus on official components. The contrib repo is open to anyone (vendors, community) to host components, but each component must have an owner who is responsible for keeping it working, responding to issues, and reviewing PRs for that component. Repo maintainers help with reviews and alignment but do not take on per-component upkeep.

What we need

For each of the three crates above, we are looking for one or more maintainers who commit to:

• Responding to issues and PRs against the crate in a reasonable timeframe.
• Keeping the crate building against the latest opentelemetry releases.
• Following OpenTelemetry conventions and reviewing changes for correctness.

Vendor employees (AWS, Datadog, Google Cloud) are especially welcome and encouraged.

Timeline

• 2 weeks from this issue being opened: if no committed maintainer has stepped up for a crate, we will announce its removal from the workspace.
• The current release of these crates on crates.io will continue to be available — removal only stops future releases from this repo.
• If a maintainer steps up later, the crate can be reinstated.

How to volunteer

Comment on this issue stating which crate(s) you are willing to maintain and your GitHub handle. We will follow up to add you to .github/component_owners.yml.

Cross-posting to the OTel Rust SIG Slack and meeting agenda.

[cijothomas]

Hi @jj22ee — you were added as the owner of opentelemetry-aws in PR #189 (Mar 2025) on behalf of the AWS X-Ray team, and we really appreciate that.

Could you let us know whether you (or someone from the AWS Observability team) is still able to maintain this crate going forward? Totally understand if priorities have shifted — just want to make sure the crate has an active owner. A quick confirmation here would be great. 🙂

[scottgerring]

Hey @cijothomas and @gruebel , now that there is dd-trace-rs built on top of opentelemetry-sdk as a first party integration, would it make sense to mark opentelemetry-datadog deprecated?

I'm happy to pick it up otherwise but from our perspective I think we should be steering customers that way (CC @bantonsson @paullegranddc )

[chinmaychahar]

Hi @cijothomas ! I’d be interested in helping maintain opentelemetry-aws.

I previously worked at AWS and currently work at Amazon, and I’d be happy to contribute toward keeping the crate maintained and up to date.

GitHub: @chinmaychahar

[cijothomas]

Hi @cijothomas ! I’d be interested in helping maintain opentelemetry-aws.

I previously worked at AWS and currently work at Amazon, and I’d be happy to contribute toward keeping the crate maintained and up to date.

GitHub: @chinmaychahar

Thanks @chinmaychahar ! Can you start by helping pending PRs already waiting for reviewers? Search for "aws" in open PRs, and help with them please. Once you do that, we can invite you to the opentelemetry organization and get your officially added as owner for aws crates.

[cijothomas]

Hey @cijothomas and @gruebel , now that there is dd-trace-rs built on top of opentelemetry-sdk as a first party integration, would it make sense to mark opentelemetry-datadog deprecated?

I'm happy to pick it up otherwise but from our perspective I think we should be steering customers that way (CC @bantonsson @paullegranddc )

Thanks. If there is no strong reason to maintain DD exporter, then lets mark it deprecated, and then plan removal in ~1 month.

[chinmaychahar]

Thanks @chinmaychahar ! Can you start by helping pending PRs already waiting for reviewers? Search for "aws" in open PRs, and help with them please. Once you do that, we can invite you to the opentelemetry organization and get your officially added as owner for aws crates.

Sure! Let me get started today

[cijothomas]

Thanks. If there is no strong reason to maintain DD exporter, then lets mark it deprecated, and then plan removal in ~1 month.

+1 to this by @bantonsson in todays SIG meeting.

[chinmaychahar]

Hi @cijothomas, I took some time to setup the aws crate and poke around locally. I've reviewed all three open AWS PRs: #510, #549, #541. Happy to continue shepherding and helping out while I get my understanding better.

Let me know about any next steps, thanks!