Offboard departing GC members and onboard new GC members

[danielgblanco]

• [ ] Update the community-members.md and and codeowners: https://github.com/open-telemetry/community/
• [ ] For each new GC member, complete an issue created with the GC Member Onboarding template.
• [ ] For each departing GC member:
  • [ ] Encourage them to join #opentelemetry-gc-alum
  • [ ] Revoke access to the systems listed the GC Member Onboarding issue.

See https://github.com/open-telemetry/community/issues/1494 for past actions.

[danielgblanco]

I think it'd be nice to have a GC member offboarding issue template with a some tasks to complete. It will basically be an inverse of the onboarding, but simpler.

[danielgblanco]

Created https://github.com/open-telemetry/community/issues/2410 to onboard @mx-psi. I don't think we need a specific issue for offboarding but rather follow the inverse.

[danielgblanco]

Created https://github.com/cncf/foundation/pull/886 to add/remove members from cncf/foundation

[danielgblanco]

One aspect that should be documented as part of this task is the discussions about GC liaison handovers between @mx-psi and @dyladan. AFAIK the aim is to move some around to ensure SIG liaisons find their best match. This conversation will happen during KubeCon NA.

[danielgblanco]

Confirmed that Dan is no longer in the Service Desk group. That was the only action remaining.