Automate org membership updates

[nikhita]

Today, GitHub admins and new membership coordinators:

1. periodically look through membership requests
2. verify if the sponsors satisfy the required criteria (not from the same company)
3. manually add the GitHub usernames to the config files one-by-one

Both GitHub Admins and the NMCs have constrained bandwidth so we should look into automating some of these.

While 1 and 2 can't really be automated because there is no way to easily verify a sponsor's employer, we should look into automating 3.

Some ideas from an old discussion with @palnabarun and @mrbobbytables:

add <gh handle> -org kubernetes -org kubernetes-sigs

add <gh handle> -team kubernetes/maintainers

Prior art for removing members in:

1. https://github.com/kubernetes/org/blob/main/hack/remove-members.sh (bash)
2. Add remove-members helper tool implemented in go #2575 (go)

[nikhita]

/assign @palnabarun
because you were interested in working on this. if you don't have the bandwidth, please unassign and we'll mark this as help-wanted

[RinkiyaKeDad]

For 2, I know we can't do it for every case but if a sponsor has specified their company on their github we could do something like

curl https://api.github.com/users/RinkiyaKeDad | jq .company

and check that the companies of the sponsors aren't the same.

[palnabarun]

@RinkiyaKeDad -- that's a great idea! 👍🏽

However, the caveat is that sometimes capitalization or the way someone has mentioned the company in that field can make the process cumbersome. We can try stripping special characters and asserting to lowercase, but would still require a level of human supervision.

[RinkiyaKeDad]

What I was initially thinking was that we could have the lowercase converted company names be commented on the issue request for the membership but I now realize this wouldn't be of much help since it would save the reviewer at max two clicks 🙂

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[nikhita]

/remove-lifecycle stale

…

On Mon, 11 Oct 2021 at 14:52, Kubernetes Triage Robot < ***@***.***> wrote: The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale - Mark this issue or PR as rotten with /lifecycle rotten - Close this issue or PR with /close - Offer to help out with Issue Triage <https://www.kubernetes.dev/docs/guide/issue-triage/> Please send feedback to sig-contributor-experience at kubernetes/community <https://github.com/kubernetes/community>. /lifecycle stale — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2812 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD24BUGBUIS6EG3UWJVON7DUGKUGJANCNFSM47TVOJIA> .

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR 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 and PRs.

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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