org icon indicating copy to clipboard operation
org copied to clipboard

Create tool for removing org members

Open nikhita opened this issue 4 years ago • 36 comments

We intend to start doing a regular cleanup of inactive members (https://github.com/kubernetes/org/issues/2013, https://github.com/kubernetes/org/pull/2047).

Removing org members means removing them from the config files in this repo. Removing them manually is tedious so we need to create an automated tool that can help us do that.

EDIT(spiffxp): https://github.com/kubernetes/org/pull/2458 merged the prior art we have in in bash, but we would rather have a tool written in something more testable, less brittle (e.g. Go)

nikhita avatar Jul 21 '20 07:07 nikhita

/assign

I'd like to take this on!

guineveresaenger avatar Jul 24 '20 20:07 guineveresaenger

great

zouyee avatar Aug 11 '20 06:08 zouyee

/assign

ameukam avatar Aug 28 '20 17:08 ameukam

🙌

guineveresaenger avatar Aug 28 '20 17:08 guineveresaenger

@nikhita @mrbobbytables How the list of inactive members will be provided to the new tool ?

ameukam avatar Aug 28 '20 19:08 ameukam

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

fejta-bot avatar Nov 26 '20 20:11 fejta-bot

/remove-lifecycle stale

zouyee avatar Nov 30 '20 02:11 zouyee

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 avatar Feb 28 '21 02:02 fejta-bot

/remove-lifecycle stale

On Sun, Feb 28, 2021 at 8:18 AM fejta-bot [email protected] wrote:

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 https://github.com/kubernetes/community. /lifecycle stale

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kubernetes/org/issues/2052#issuecomment-787223436, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD24BUEJKLYE7Z5T4RNMTXDTBGVGTANCNFSM4PDIKUIQ .

nikhita avatar Feb 28 '21 04:02 nikhita

@nikhita is this something we can turn into a GSoC project?

dims avatar Feb 28 '21 18:02 dims

@dims this is probably too much of a little project. It's essentially to convert this bash script to go: https://github.com/kubernetes/org/pull/2458

mrbobbytables avatar Feb 28 '21 18:02 mrbobbytables

Ack @mrbobbytables

dims avatar Feb 28 '21 18:02 dims

It's essentially to convert this bash script to go: #2458

To me, that sounds like enough for...

/help /kind cleanup /priority important-longterm

spiffxp avatar Mar 10 '21 17:03 spiffxp

@spiffxp: This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to this:

It's essentially to convert this bash script to go: #2458

To me, that sounds like enough for...

/help /kind cleanup /priority important-longterm

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.

k8s-ci-robot avatar Mar 10 '21 17:03 k8s-ci-robot

/assign

I would like to work on this 😄

daemon1024 avatar Mar 15 '21 10:03 daemon1024

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 avatar Jul 05 '21 03:07 fejta-bot

/remove-lifecycle stale

nikhita avatar Jul 05 '21 10:07 nikhita

/milestone v1.23

spiffxp avatar Aug 17 '21 19:08 spiffxp

This is only about how to remove member by a script. But how to provide the list of inactive members?

The docs only say that we can check inactive members on devstats.cncf.io. But there is no simple query for that.

I was reminded to check inactive members per https://github.com/kubernetes/kubernetes/pull/104848#issuecomment-915541959

pacoxu avatar Sep 09 '21 07:09 pacoxu

devstats.cncf.io

I see devstats give us the list of contributors based on the period like last 1year, 2 year etc.. based on the time limit we can get that list and negate with the total list to find the list of members we need to remove.

mkumatag avatar Sep 29 '21 17:09 mkumatag

What we've done in the past is pull the stats for each release cycle which gives us an explicit period of time to track contributions, so if a person has not done anything in the past 5 releases (20 months now that releases are 4 months), we can safely remove.

mrbobbytables avatar Sep 29 '21 21:09 mrbobbytables

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 avatar Dec 28 '21 23:12 k8s-triage-robot

/remove-lifecycle stale

zouyee avatar Jan 07 '22 06:01 zouyee

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 avatar Apr 07 '22 06:04 k8s-triage-robot

/remove-lifecycle stale This is still needed. /milestone v1.25

ameukam avatar Apr 07 '22 08:04 ameukam

@ameukam: The provided milestone is not valid for this repository. Milestones in this repository: [v1.21, v1.22, v1.23]

Use /milestone clear to clear the milestone.

In response to this:

/remove-lifecycle stale This is still needed. /milestone v1.25

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.

k8s-ci-robot avatar Apr 07 '22 08:04 k8s-ci-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 avatar Jul 06 '22 09:07 k8s-triage-robot

/remove-lifecycle stale

palnabarun avatar Jul 28 '22 06:07 palnabarun

/remove-lifecycle stale

On Thu, 7 Apr 2022 at 11:42, 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:

Please send feedback to sig-contributor-experience at kubernetes/community https://github.com/kubernetes/community.

/lifecycle stale

— Reply to this email directly, view it on GitHub https://github.com/kubernetes/org/issues/2052#issuecomment-1091118278, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD24BUGXJC34AY5USKAMBO3VDZ4ENANCNFSM4PDIKUIQ . You are receiving this because you were mentioned.Message ID: @.***>

nikhita avatar Oct 11 '22 07:10 nikhita

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

This bot triages 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 PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this 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 avatar Feb 08 '23 08:02 k8s-triage-robot