SIG Autoscaling: Leadership Change

[gjtempleton]

SIG/WG name:

SIG Autoscaling

Onboarding Lead(s):

@towca @raywainman @jackfrancis

Offboarding Lead(s):

@MaciekPytel

Link to discussion:

https://docs.google.com/document/d/1RvhQAEIrVLHbyNnuaT99-6u9ZUMp7BfkPupT2LAZK7w/edit# https://groups.google.com/g/kubernetes-sig-autoscaling/c/5bLPrT8BNlw

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 (ran make). NOTE: If offboarding, remember to add to emeritus.
• [x] Updated OWNERS_ALIASES in kubernetes/org.
• [x] Updated milestone maintainers team in kubernetes/org.
• [x] Checked for and updated any other potential teams in kubernetes/org.
• [x] Updated OWNERS_ALIASES in kubernetes/enhancements.
• [ ] Updated OWNERS_ALIASES in kubernetes/k8s.io.
• [ ] Updated feature-approvers in OWNERS_ALIASES in kubernetes/kubernetes (when applicable)
• [x] Updated membership of the leads mailing list
• [x] Updated membership for any other mailing list / groups.
• [x] Added to #chairs-and-techleads slack channel.
• [x] Updated ownership of group leads mailing list.
• [ ] Updated ownership of group mailing list.
• [ ] 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 autoscaling

[gjtempleton]

Have added @raywainman and @jackfrancis as well as the SIG is now adopting and filling the SIG Tech Lead roles as per https://groups.google.com/g/kubernetes-sig-autoscaling/c/5bLPrT8BNlw

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[towca]

/remove-lifecycle rotten

[raywainman]

I'm cleaning this up as part of https://github.com/kubernetes/community/issues/8629. I think this can just be closed as a duplicate.