Onboard new contribex leads

[nikhita]

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

• Discuss the proposed changes with the current leadership.

Discuss with the SIG and wider community

• 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:
  • intent to step down as the current lead
  • if nominating another lead
    • 1-2 lines about why they are being nominated
    • contacts to privately reach out to for questions (current leads)
      or concerns (current leads + steering-private) about the nomination
  • lazy consensus deadline of at least one week

New lead requirements

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

Updating artifacts

• k/community - sigs.yaml, OWNERS, autogenerated content - sig-contribex: add new leads #7247
• k/org - GitHub teams, OWNERS - Add new leads to sig-contribex teams org#4153
• k/test-infra - config/jobs/kubernetes/community/OWNERS - Add new contribex leads to k/community job OWNERS test-infra#29257
• k/k - .github/OWNERS, OWNERS_ALIASES - Add new contribex leads to sig-contribex-approvers kubernetes#117187
• k/enhancements - OWNERS - Add new contribex leads to OWNERS_ALIASES enhancements#3946
• k/k8s.io - groups/sig-contributor-experience/OWNERS - Onboard new contribex leads k8s.io#5112
• k-sigs/contributor-playground - OWNERS - Add new contribex leads to OWNERS kubernetes-sigs/contributor-playground#1075

Communication Properties

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

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

[MadhavJivrajani]

@nikhita @mrbobbytables - Also created cncf/foundation#538

[mrbobbytables]

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]

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 #5442. Do you remember what we ended up doing there?

[mrbobbytables]

Just checking back in, are we all good here?

[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

[Priyankasaggu11929]

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]

I'd ping @amye for assistance. This is related to cncf/foundation#538

[amye]

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

[Priyankasaggu11929]

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 . 🙂

[cblecker]

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

[Priyankasaggu11929]

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

[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

[palnabarun]

/remove-lifecycle rotten