SIG Cloud Provider: Leadership Change

bridgetkromhout commented 1 year ago

SIG/WG name:

SIG Cloud Provider

Onboarding Lead(s):

bridgetkromhout, elmiko

Offboarding Lead(s):

N/A

Link to discussion:

https://groups.google.com/g/kubernetes-sig-cloud-provider/c/BAh7gGZhfvo

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.
[X] Updated OWNERS_ALIASES in kubernetes/k8s.io.
[x] 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.
[ ] Updated ownership of group calendar.
[ ] Updated access/teams in 1password. (Contact ContribEx leads to complete)

Additional Information:

Discussed/voted on SIG Cloud Provider calls in March-April 2023 as noted in meeting minutes: https://docs.google.com/document/d/1OZE-ub-v6B8y-GuaWejL-vU_f9jsjBbrim4LtTfxssw/edit?usp=sharing

Note: Andrew Sy Kim and Nick Turner, the previous chairs, moved to be tech leads.

mrbobbytables commented 1 year ago

/sig cloud-provider

bridgetkromhout commented 1 year ago

Looks like we also needed these updates: https://github.com/kubernetes/k8s.io/pull/5781 and https://github.com/kubernetes/test-infra/pull/30573.

k8s-triage-robot commented 7 months ago

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 commented 6 months ago

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 commented 5 months ago

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 commented 5 months ago

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

In response to [this](https://github.com/kubernetes/community/issues/7340#issuecomment-2022408849): >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][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

kubernetes / community