SIG Auth: Leadership Change

[enj]

SIG/WG name:

Auth

Onboarding Lead(s):

aramase, micahhausler

Offboarding Lead(s):

mikedanese

Link to discussion:

https://groups.google.com/a/kubernetes.io/g/dev/c/L_JkfCRexxM

Prerequisites for new leads:

• [x] Are a Kubernetes Org member
• [x] Have completed the Inclusive Open Source Community Orientation course

Onboarding / Offboarding tasks:

• [x] Updated sigs.yaml and associated generated files -> #8404
• [x] Updated OWNERS_ALIASES in kubernetes/org -> https://github.com/kubernetes/org/pull/5493
• [x] Updated milestone maintainers team in kubernetes/org -> https://github.com/kubernetes/org/pull/5493
• [x] Checked for and updated any other potential teams in kubernetes/org -> https://github.com/kubernetes/org/pull/5493
• [x] Updated OWNERS_ALIASES in kubernetes/enhancements -> https://github.com/kubernetes/enhancements/pull/5221
• [x] Updated OWNERS_ALIASES in kubernetes/k8s.io -> https://github.com/kubernetes/k8s.io/pull/7950
• [ ] ~~Updated feature-approvers in OWNERS_ALIASES in kubernetes/kubernetes (when applicable)~~
• [ ] Updated membership of the leads mailing list
• [ ] Updated membership for any other mailing list / groups.
• [x] Added to #chairs-and-techleads slack channel.
• [ ] Updated ownership of group leads mailing list.
• [ ] Updated ownership of group mailing list.
• [x] Updated ownership of group calendar.
• [ ] Updated access/teams in 1password. (Contact ContribEx leads to complete)
• [ ] Update permissions for the corresponding Youtube playlists. (Contact YouTube moderators)

Additional information:

No response

Labels:

/sig auth /assign

cc @ritazh @aramase @micahhausler @liggitt @deads2k @mikedanese

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[aramase]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale