Trask Stalnaker

> I'd need to reach out to our enterprise owners in the LF/CNCF for definitive answer but from what I can tell we're on an Enterprise plan that should come...

> We'll try again soon with a simpler repository (or maybe even a test repo?) to see what we can do about EasyCLA and not blocking PR actions. It may...

> assume this is accepted practice! check out https://github.com/open-telemetry/community/blob/main/docs/how-to-configure-new-repository.md#collaborators-and-teams > If requested, `foo-maintainers` will be granted `Admin` permissions, and in return they must document any changes they make to the...

Oops, yes, thanks Cc @open-telemetry/technical-committee

> Julian has "Maintainer" tag this means they are a maintainer of the team, and can add and remove members it looks like that team wasn't set up quite right,...

hi @Spazzy757! can you open this as a project proposal PR against the [community](https://github.com/open-telemetry/community) repo? check out https://github.com/open-telemetry/community/blob/main/project-template.md and https://github.com/open-telemetry/community/tree/main/projects

> nit: > > > It adds more [...] responsibilities to that group > > Shouldn't each "sponsor-to-be" acknowledge that they want to be a sponsor (e.g. by asking for...

(cc @open-telemetry/specs-semconv-maintainers)

> The challenge is when these things are done via GitHub actions they don't trigger other workflows. There are a few recommendations published by GitHub to solve this: https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md#workarounds-to-trigger-further-workflow-runs would...

My initial inclination would be to have these deviations documented somewhere in this repository, where they will get visibility and implicit sign-off from TC members via PR.