Hiya. Not sure who might know this (likely GC/TC @open-telemetry/governance-committee @open-telemetry/technical-committee ), but the Android SIG maintainers are entertaining the idea of enabling the Google Play SDK Console (tracking issue here) for our agent. This utility would allow us (Android SIG maintainers) to better understand if/how the SDK might be (mis)behaving, and we think it should provide some useful data that could help inform direction around project direction/features. Even more information here: https://play.google.com/sdk-console/about/

So I guess first question is: Are there any concerns about an otel project using this? I assume no, and that we have the agency to do so if we wish.

The main question is around group/collective identity and how this relates to Google's view of ownership of the maven artifacts after signup. As one of the maintainers, I could just go sign up and use my corporate google account/identity, but this seems far from ideal, because it tells google that the "owernship" of io.opentelemetry.android in maven central is somehow tied to [email protected] -- which isn't entirely true, and would also be a problem if something were to happen to me.

Do we have any existing/prior art for creating or using any existing "shared" otel google accounts? If so, what would be my next step to leverage that? If not, do we have any creative ideas about how to prevent this control from being tied to a single person?

Thanks thanks! 🍻