Subproject Lead access for Grace, Kat & Marko

[justaugustus]

trafficstars

Subproject leads — Please do not proceed with additional access grants until https://github.com/kubernetes/sig-release/issues/2515 is resolved.

GitHub Username

@gracenng @katcosgrove @xmudrii

Chair/Technical Lead role

e.g., Chair, Technical Lead

Chair and Technical Lead Onboarding

All pull requests within these checklists should be marked with an explicit hold and only released once approved by a SIG Release (subproject) owner.

• [ ] Addition of a new Release Manager has been discussed with and approved by SIG Release owners
• [ ] Ensure new Chair/Technical Lead:
  • [ ] Has joined the following mailing lists:
    • kubernetes-sig-release
    • kubernetes-release-team
    • kubernetes-dev
    • kubernetes-announce
    • release-managers
    • release-managers-private
  • [ ] Has joined the following Slack channels:
    • #sig-release
    • #release-management
  • [ ] Is a Kubernetes GitHub org member
  • [ ] Is part of the @kubernetes/sig-release-admins GitHub team
• [ ] Update Release Managers page to include the new Chair or Technical Lead

cc: @kubernetes/sig-release-admins

[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

[xmudrii]

I think we still have to follow up on this /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

[xmudrii]

/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

[xmudrii]

/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

[xmudrii]

/remove-lifecycle stale