-
Notifications
You must be signed in to change notification settings - Fork 677
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create tool for removing org members #2052
Comments
/assign I'd like to take this on! |
great |
/assign |
🙌 |
@nikhita @mrbobbytables How the list of inactive members will be provided to the new tool ? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle stale
…On Sun, Feb 28, 2021 at 8:18 AM fejta-bot ***@***.***> 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
<#2052 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD24BUEJKLYE7Z5T4RNMTXDTBGVGTANCNFSM4PDIKUIQ>
.
|
@nikhita is this something we can turn into a GSoC project? |
Ack @mrbobbytables |
To me, that sounds like enough for... /help |
@spiffxp: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
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. |
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 kubernetes/kubernetes#104848 (comment) |
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. |
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. |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
@ameukam: The provided milestone is not valid for this repository. Milestones in this repository: [ Use In response to this:
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. |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/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:
- 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
—
Reply to this email directly, view it on GitHub
<#2052 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD24BUGXJC34AY5USKAMBO3VDZ4ENANCNFSM4PDIKUIQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale
…On Wed, 8 Feb 2023 at 13:57, Kubernetes Triage Robot < ***@***.***> wrote:
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
<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
—
Reply to this email directly, view it on GitHub
<#2052 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD24BUAT25NAVQNKSMF5NH3WWNKIFANCNFSM4PDIKUIQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I can help with this. Looks like we need to add a function Then to keep this automated, we can define a periodic prow job that runs every 2 years or so. What do you think folks? I don't want to submit a PR right away maybe someone has been working on that. |
I wanted to offer to adapt a github action that some of us built over in: The description of the features is in: and a general diagram is at: |
Ppart of the requested functionality was added recently in (thanks @palnabarun): from: #2052 (comment)
@palnabarun, is this the only part left for implementation here? |
I don't think we should run a Prow job for doing the audit. A lot of actions done in the process require human knowledge and intervention. |
I was thinking about having a Prow job, for just opening an issue with a And then GH admins do the manual process for reviewing the list & actual removal. |
We intend to start doing a regular cleanup of inactive members (#2013, #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): #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)
The text was updated successfully, but these errors were encountered: