SIG Docs chair transition

[zacharysarah]

ref: kubernetes/website#23797

🟢 OK TO MERGE 🟢

Don't merge this PR until all conditions are true:

• all governance pieces of #23797 are approved
• Date equal to or later than September 15th, 2020

Description

This PR updates repo permissions and contacts for @irvifa becoming a chair and @zacharysarah transitioning to chair emeritus.

/assign @irvifa @jimangel @kbarnard10

[k8s-ci-robot]

@zacharysarah: GitHub didn't allow me to assign the following users: irvifa.

Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

ref: kubernetes/website#23797

🟢 OK TO MERGE 🟢

Don't merge this PR until all conditions are true:

• all governance pieces of #23797 are approved
• Date equal to or later than September 15th, 2020

Description

This PR updates repo permissions and contacts for @irvifa becoming a chair and @zacharysarah transitioning to chair emeritus.

/assign @irvifa @jimangel @kbarnard10

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.

[jimangel]

/lgtm
/approve

[zacharysarah]

@irvifa 👋 Looks like you need to open a PR in kubernetes/community to add yourself to the kubernetes-sigs org.

[irvifa]

Hi @zacharysarah is this under sig docs cmiiw?

[zacharysarah]

@irvifa Yes, this repo is how SIG Docs currently generates API reference docs. (Hopefully not for too much longer.)

[irvifa]

@zacharysarah Noted then. I already create an issue and PR for this.

[irvifa]

/retest

[irvifa]

Hi @zacharysarah do we need to do something about the k8s label? Since I already merged my PR to satisfy the condition

[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

[jimangel]

/remove-lifecycle stale
/verify-owners

[jimangel]

/lgtm
/approve
(take two!)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jimangel, zacharysarah

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jimangel,zacharysarah]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment