Community: github: audit and remove stale org members

[cblecker]

We have no policy around inactivity for org members.

We should do something like:

• establish standard for what defines "inactivity" (6 months perhaps?)
• determine a way to get a report of who's inactive (devstats?)
• create a policy on how often we check for inactivity, how do we notify those contributors, and then the actual process for PRing the removal

[nikhita]

/priority important-longterm

[nikhita]

/kind documentation

Since this revolves around creating the policy first.

[nikhita]

determine a way to get a report of who's inactive (devstats?)

One example of this for OWNERS files: https://github.com/kubernetes/kubernetes/issues/76269

[spiffxp]

ref: https://github.com/kubernetes/community/issues/1808 for owners files

[nikhita]

xref https://github.com/kubernetes/org/issues/966

[mrbobbytables]

/assign

[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

[mrbobbytables]

/remove-lifecycle stale

[BenTheElder]

Discussed again today, we seem to have a lot of these.
How do we get consensus on the standards? Sounds like @mrbobbytables already more or less has the data.

[BenTheElder]

Is there a related issue for "get SIGs to add new OWNERS"? I haven't found it yet.

[spiffxp]

/milestone v1.19
We discussed a proposal from @mrbobbytables during github-management meeting today, agreed to bring it forward to sig-contributor-experience next

[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

[nikhita]

/remove-lifecycle stale

On Thu, Jun 25, 2020 at 12:22 AM fejta-bot [e-mail] 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-testing, kubernetes/test-infra and/or fejta
https://github.com/fejta.
/lifecycle stale

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/community/issues/3179#issuecomment-649003008,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD24BUHWB7R2JGHMFLU2EHDRYJDO7ANCNFSM4GTOIHTQ
.

[mrbobbytables]

The members have been removed, there are a few blocks on on updating owners with code freeze etc but those will be resolved soon.
With that, I think this is good enough to call done \o/

[mrbobbytables]

Going to go ahead and close it 👍 If there is any other follow up please go ahead and reopen
/close

[k8s-ci-robot]

@mrbobbytables: Closing this issue.

In response to this:

Going to go ahead and close it 👍 If there is any other follow up please go ahead and reopen
/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.