SIG-Multicluster: Leadership Change

[skitt]

SIG/WG name:

SIG Multicluster

Onboarding Lead(s):

skitt

Offboarding Lead(s):

pmorie

Link to discussion:

https://groups.google.com/g/kubernetes-sig-multicluster/c/xhj2OnFO-8M

Prerequisites for new leads:

• Are a Kubernetes Org member
• 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.
• 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.
• 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 multicluster

PRs:

• SIG-Multicluster leadership change: pmorie emeritus, skitt co-chair #7963
• SIG-MC leadership change: pmorie emeritus, skitt co-chair org#5043
• SIG-MC leadership change: pmorie emeritus, skitt co-chair k8s.io#6932
• SIG-Multicluster leadership change: pmorie emeritus, skitt co-chair enhancements#4749

[skitt]

/cc @JeremyOT

[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

[skitt]

/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

[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

[k8s-triage-robot]

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.