Trask Stalnaker

> I think we would want to look at what's currently being used, see if there's opportunities for de-duplication, and perhaps provide best practices around things like tooling for secret...

btw, it looks like GitHub Actions Arm support will be in public preview pretty soon now: https://github.com/github/roadmap/issues/955

@atoulme I found this in the open-telemetry github org insights, does this help at all? 

maybe run arm jobs only on `main` and not on PRs? (if you aren't doing that already)

> From a user perspective, I expect all the repositories named `opentelemetry-XXX-instrumentation` will be an agent-like thing that does instrumentation in runtime (this is correct for Java, Python, .NET, JS)....

> The `opentelemetry-xxx-instrumentation` repository should provide automated instrumentation solutions, whether it's eBPF, Java agent, compile-time instrumentation, or something else. It different from manual instrumentation, which should be placed under the...

I support

hi @sourabh1007! can you confirm the requirements above by checking the boxes?

I support

> I ... think I can count as a sponsoring member as well? currently the sponsoring members need to be TC/GC or someone those groups have specifically agreed to delegate...