Onboard new contribex leads

nikhita commented 1 year ago

Congratulations @kaslin, @palnabarun, @MadhavJivrajani and @Priyankasaggu11929! 🚀

Some items in the checklist are derived from https://github.com/kubernetes/community/blob/master/contributors/chairs-and-techleads/leadership-changes.md.

Discuss with SIG leadership

[x] Discuss the proposed changes with the current leadership.

Discuss with the SIG and wider community

[x] Send an email to the SIG/WG/UG mailing list and cc the kubernetes-dev mailing list: https://groups.google.com/g/kubernetes-dev/c/TYwMb3lbuyE At a minimum, the email should contain:
- [x] intent to step down as the current lead
- [x] if nominating another lead
- [x] 1-2 lines about why they are being nominated
- [x] contacts to privately reach out to for questions (current leads) or concerns (current leads + steering-private) about the nomination
- [x] lazy consensus deadline of at least one week

New lead requirements

[x] If nominating another lead, ensure that they
- [x] are a Kubernetes GitHub org member
- [ ] have completed the Inclusive Leadership Training (Inclusive Open Source Community Orientation course)

Updating artifacts

[x] k/community - sigs.yaml, OWNERS, autogenerated content - https://github.com/kubernetes/community/pull/7247
[x] k/org - GitHub teams, OWNERS - https://github.com/kubernetes/org/pull/4153
[x] k/test-infra - config/jobs/kubernetes/community/OWNERS - https://github.com/kubernetes/test-infra/pull/29257
[x] k/k - .github/OWNERS, OWNERS_ALIASES - https://github.com/kubernetes/kubernetes/pull/117187
[x] k/enhancements - OWNERS - https://github.com/kubernetes/enhancements/pull/3946
[x] k/k8s.io - groups/sig-contributor-experience/OWNERS - https://github.com/kubernetes/k8s.io/pull/5112
[x] k-sigs/contributor-playground - OWNERS - https://github.com/kubernetes-sigs/contributor-playground/pull/1075

Communication Properties

[x] Update the following mailing lists:
- [x] leads@kubernetes.io - https://github.com/kubernetes/k8s.io/pull/5112
- [x] contribex leads mailing list
- [x] owner for sig-contribex mailing list
- [x] contributors@kubernetes.io
[x] Add new leads to #chairs-and-tech-leads slack channel
[x] Grant new leads access to zoom credentials
[x] Grant new leads access to YouTube credentials (through proxy by contributors@)
[x] Add new leads to CNCF maintainer lists (ping Ihor?)
- [x] https://lists.cncf.io/g/cncf-kubernetes-maintainers
- [x] CNCF service desk access

/sig contributor-experience cc @jberkus @mrbobbytables @cblecker

MadhavJivrajani commented 1 year ago

@nikhita @mrbobbytables - Also created https://github.com/cncf/foundation/pull/538

mrbobbytables commented 1 year ago

contributors@kubernetes.io

contributors@ is a named account, they will have access to the pw via 1password (invites out)

I think you meant community@?

nikhita commented 1 year ago

contributors@ is a named account, they will have access to the pw via 1password (invites out)

I think you meant community@?

@mrbobbytables I just copied the template rom https://github.com/kubernetes/community/issues/5442. Do you remember what we ended up doing there?

mrbobbytables commented 1 year ago

Just checking back in, are we all good here?

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

Priyankasaggu11929 commented 10 months ago

Add new leads to CNCF maintainer lists https://lists.cncf.io/g/cncf-kubernetes-maintainers

For me, ^ is still pending. I'm getting below prompt.

@nikhita @mrbobbytables @cblecker, it would still be pinging Ihor or someone else from CNCF for getting it approved?

/remove-lifecycle stale

cblecker commented 9 months ago

I'd ping @amye for assistance. This is related to https://github.com/cncf/foundation/pull/538

amye commented 9 months ago

Mailing lists are for Steering Committee members! Should this be updated in here?

Priyankasaggu11929 commented 9 months ago

Mailing lists are for Steering Committee members! Should this be updated in here?

@cblecker, @mrbobbytables confirmed offline, adding contribex leads to the asked ML is not needed. No action needed. Thanks @amye . :slightly_smiling_face:

cblecker commented 7 months ago

Looks like all that's left here is confirmation of the inclusive leadership training?

Priyankasaggu11929 commented 7 months ago

Confirming completion of the Inclusive Open Source Community Orientation LFC102 training (Certificate ID number - LF-pp8is78xko)

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

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

palnabarun commented 3 months ago

/remove-lifecycle rotten

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