SIG lead lifecycle needs to be documented

[castrojo]

When a SIG lead moves on we need to document a few things. There are pending governance things here but this issue will document the technical changes at a minimum.

• Old lead
  • unsubscribe from their sig leaders list.
  • Removal as leader from sigs.yaml
• New lead
  • Subscribe to the sig leaders list.
  • Need the Zoom credentials to record meetings
  • Need Youtube collaboration URL, perhaps a new one should be generated?
  • Addition as leader in sigs.yaml and then regenerate the pages.

Announcements to:

• That SIG's internal list
• kubernetes-dev list
• Mention in the announcements of a community meeting

[castrojo]

Marking as contrib-ex but blocking on SIG charters, governance, etc.

/sig contributor-experience

[castrojo]

See also: #1650

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[cblecker]

Governance stuff should be done, but the process stuff might need to still go in.
/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[cblecker]

/remove-lifecycle stale
/lifecycle frozen

[parispittman]

@jonasrosland + @castrojo will work on proposing a solution after SC election

[nikhita]

/area community-management
/priority important-longterm

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[markjacksonfishing]

/remove-lifecycle stale

[mrbobbytables]

I think this can be accomplished this cycle, we need to add more items to the chairs and TLs guides
/milestone v1.20

[mrbobbytables]

Review this and determine if this can be closed -
Ref: https://github.com/kubernetes/community/blob/master/contributors/chairs-and-techleads/leadership-changes.md

[mrbobbytables]

/unassign @jonasrosland @castrojo
/assign @alisondy @mrbobbytables
looping in so we can document that change over.

[mrbobbytables]

We should convert the leadership change doc into an issue template that is closed when all items are checked off.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ger1964jou]

Bonjour le monde