Pablo Baeyens

Note: we need to update the GC onboarding template to reflect the new meeting time as well as the governance committee Google group

> No edit access GC (or GC-TC) meeting notes I removed access to the meeting notes (for future offboarding processes, I switched to using the Google group so removal from...

> I am not convinced that we should do this because it changes quite a few options and it can be disruptive to end users, specially given that, because of...

> I'm supportive of this approach. I think we can finalize the migration before marking confighttp 1.0 Since the OTLP exporter and the OTLP receiver are marked as 1.0 I...

Hi @Manuelraa! You can provide your configuration in multiple files by using the `${file:/path/to/file}` syntax. You can see an example [here](https://github.com/open-telemetry/opentelemetry-collector/tree/main/service#embedding-other-configuration-providers). Would that work for you?

Alright, thanks for the details. I moved this to the opentelemetry-collector repository then, since this is a confmap feature.

@austinlparker and @jsuereth should know how this was set up. The current CAA record affects both opentelemetry.io and all its subdomains

That is my understanding from the RFC, yes (provided the certificate authority attempting to issue the certificate supports this)

@open-telemetry/semconv-rpc-approvers I would love to have your opinion on this PR. My interpretation of https://opentelemetry.io/blog/2025/stability-proposal-announcement/#instrumentation-and-convention-goals is that this would be fine to have enabled by default, but if you believe...

@open-telemetry/go-approvers is using Unix sockets supported by OTel Go?