Tyler Yahn

@jj22ee linking my response from [here](https://github.com/open-telemetry/opentelemetry-go-contrib/issues/5545#issuecomment-2145895167): > @jj22ee I see you are not already a [CNCF project member ](https://github.com/open-telemetry). This is one of the [requirements](https://github.com/open-telemetry/opentelemetry-go-contrib/blob/main/CONTRIBUTING.md#requirements) we have for becoming a...

> @Aneurysm9 @MrAlias I'm willing to be code owner for this component Awesome @wangzlei! It looks like you meet all the requirements to become a Code Owner of this module....

This doesn't include any of the details discussed during yesterdays SIG meeting regarding rolling out the "opt-in" phase over multiple releases for all the instrumentation libraries.

Going to hold the next release until we can resolve the environment variable issue.

Closing. We have adopted this plan and are moving forward with it.

> Is the ec2 detector at all meant to run on non ec2 machines? No it is not. Though, it should fail gracefully when it is not running there. I...

We should determine the SLA for the AWS response time to the EC2 metadata endpoint. The detector should then create a child context that has that set as its timeout...

Resolved by https://github.com/open-telemetry/opentelemetry-go-contrib/pull/6671

This module will need to be added to the project [`versions.yaml`](https://github.com/open-telemetry/opentelemetry-go-contrib/blob/851b2fd97fa45bb502cc094b6e3e84464a140fc3/versions.yaml#L77) under the unreleased section.

I think `otelconf` should be also be considered.