ContribEx: Leadership Change - cblecker, nikhita, mrbobbytables

mrbobbytables commented 8 months ago

SIG/WG name:

SIG Contributor Experience

Onboarding Lead(s):

No response

Offboarding Lead(s):

cblecker, nikhita, mrbobbytables

Link to discussion:

https://github.com/kubernetes/community/pull/7603

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

Additional information:

No response

Labels:

/sig contributor-experience

cblecker commented 8 months ago

Opened the following OWNERS_ALIASES updates: https://github.com/kubernetes/enhancements/pull/4344 https://github.com/kubernetes/k8s.io/pull/6115 https://github.com/kubernetes/org/pull/4599

MadhavJivrajani commented 8 months ago

Created:

k8s-triage-robot commented 4 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

cblecker commented 4 months ago

/lifecycle active /assign @kaslin @palnabarun

mrbobbytables commented 4 months ago

I updated the tasks that I know about, I think theres a few group memberships that ownership should be updated on (e.g. leads list)

palnabarun commented 4 months ago

leads@ is upto date (in terms of adding new leads).

cblecker commented 3 months ago

Anything else left on this? I checked off the last few items that I know are done and don't see anything further.

k8s-triage-robot commented 1 week 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

kubernetes / community