Cleanup Inactive Org Members

[palnabarun]

Following is the list of inactive members who are slated to be removed from the Kubernetes organizations:

TBD (pending on a data import from devstats)

Tasks

• Get the data import
• Find members to remove and teams they belong to
• Ping and wait for people to let us know if they have been contributing to non-code areas
• Remove the inactive members

[palnabarun]

/assign
/assign @nikhita @MadhavJivrajani @RinkiyaKeDad

[palnabarun]

Previous Instances of cleanup: #2456, #2076

[mrbobbytables]

/assign
(just to keep it on my radar)

[mrbobbytables]

/retitle Cleanup Inactive Org Members -Q1 2022

[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

[nikhita]

/unassign @nikhita @MadhavJivrajani @RinkiyaKeDad

Let's re-assign when tasks are being picked up.

@palnabarun do you know how to import the required data from devstats? If yes, can you also help document this so either of us can pick this up in the future?

[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

[Sea-n]

We still need to cleanup inactive org members.
/remove-lifecycle stale

It's being postponing, remove the time from issue title.
/retitle Cleanup Inactive Org Members

[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

[MadhavJivrajani]

/remove-lifecycle stale
/lifecycle frozen

[nikhita]

/remove-lifecycle frozen

@palnabarun or @mrbobbytables we've added a lot of members in the last few months. Do y'all have bandwidth to cleanup inactive members soon?

[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

[nikhita]

/remove-lifecycle stale

[nikhita]

/remove-lifecycle rotten

[pacoxu]

/assign
I could like to help once we need to do a cleanup.

[palnabarun]

PR #4291 introduces a command to audit the orgs. There are few TODOs to be done as followups after it is merged, most important being removing org members using the korg toolkit. I will take that up next week to ease the removal process.

[pacoxu]

It seems that we did not cleanup inactive org members for two years.

Can I try with @palnabarun's tool in the PR to do a cleanup this month?

[pacoxu]

The removal list is at https://gist.github.com/pacoxu/21622b30d3511d8a9df8507f58926769.

I would open a new issue "Clean up inactive members - Sept 2023" to track the removal process if there is no question about it.

• I found the current generated list is 692. The last one is only 59 members. Is it normal? Should I do a double-check 🤣？

[palnabarun]

@pacoxu I will send comms about the removal next week after verifying the audit script. We need to give the community a heads-up before removing org members.

Also, I don't think we need to open a new issue. We can work out of this.

[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

[palnabarun]

/remove-lifecycle stale

[palnabarun]

Following up on #4726

/close

[k8s-ci-robot]

@palnabarun: Closing this issue.

In response to this:

Following up on #4726

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