Alexander Wert

@open-telemetry/technical-committee @open-telemetry/governance-committee Can you help us with that, please? We'd like to kick-off the repo asap, so we can start the work on integrating the agent into OTel.

> > I personally like option 2. As far as I remember we have never done this in the past, so we will need to double check the implications. I...

@trask is there an update already on the legal ticket?

> Is there an expected time for the migration of otel-profiling-agent to open-telemetry? We are blocked by / waiting for the reply on the above-mentioned legal ticket.

> Is you intention to enrich individual telemetry signals or resources? @lmolkova The intention of the GeoIP processor is to have a flexible processor that can derive geo information from...

> Effectively, `geo` namespace becomes something that's usually embedded and not used as stand-alone. > This way we can enrich signals with geo information unambiguously and on any level (application,...

@open-telemetry/specs-semconv-approvers Can we get more general approvals on this one please? We already have a bunch of the profiling SIG's approvals, just missing an additional general semconv SIG approval.

@ezimuel Can you please update this PR with the new semconv folder structure? Thanks

@tigrannajaryan This is another case for the need of mutable resource attributes. Is there already some central place where the Entity WG is tracking these cases? If not would it...

can this and the parent issue be closed (since we moved out the follow-ups into separate issues)?