SIG etcd: Leadership Change

[siyuanfoundation]

SIG/WG name:

SIG etcd

Onboarding Lead(s):

siyuanfoundation

Offboarding Lead(s):

wenjiaswe

Link to discussion:

https://groups.google.com/g/etcd-dev/c/1I9Q8i97Lts/m/WiYQK0MAAgAJ

Prerequisites for new leads:

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

Onboarding / Offboarding tasks:

• [ ] Updated sigs.yaml and associated generated files (ran make). NOTE: If offboarding, remember to add to emeritus.
• [ ] Updated OWNERS_ALIASES in kubernetes/org.
• [x] Updated milestone maintainers team in kubernetes/org.
• [ ] Checked for and updated any other potential teams in kubernetes/org.
• [ ] Updated OWNERS_ALIASES in kubernetes/enhancements.
• [ ] Updated OWNERS_ALIASES in kubernetes/k8s.io.
• [x] 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.
• [ ] Added to #chairs-and-techleads slack channel.
• [ ] 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 etcd /assign @siyuanfoundation

[siyuanfoundation]

/cc @wenjiaswe

[wenjiaswe]

/cc @serathius @ahrtr @jmhbnz @ivanvc

Congratulations Siyuan! Well deserved! Thank you for your consistent, high quality contribution to etcd and kubernetes. I am more than confident you will be a great sig lead!

[wenjiaswe]

• [x] Added to #chairs-and-techleads slack channel.
• [x] Updated membership of the leads mailing list - done for both @siyuanfoundation and @ivanvc , Ivan became SIG-etcd chair a few months ago. I removed myself as well.
• [x] Updated ownership of group leads mailing list. (sent the request to owner and manager of the group, will mark this as done.
• [ ]

[serathius]

+1

[jmhbnz]

+1

[ivanvc]

+1

[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

[palnabarun]

@siyuanfoundation @wenjiaswe This issue has now gotten stale. Can you please check if the remaining onboarding are already done?

[siyuanfoundation]

this is done.