search

kubernetes / org

Meta configuration for Kubernetes Github Org
Apache License 2.0
240 stars 669 forks source link

Clean up inactive members - Jan 2021 #2456

Closed mrbobbytables closed 3 years ago

mrbobbytables commented 3 years ago

This is the list of inactive members that are slated to be removed from our Github Orgs. They have had no devstats recorded since July 1 2019.

Inactive Members:

Repos with inactive owners:

Kubernetes Org

Kubernetes SIGs Org

Kubernetes client Org

dims commented 3 years ago

+1 from me!

mrbobbytables commented 3 years ago

There is a limit on pings per post, this is the remainder that did not get pinged above:

heckj commented 3 years ago

@mrbobbytables 👋 Ola - yes, unfortunately inactive when it comes to Kubernetes. Not sure what you need from me or what this entails, but I thought I'd confirm at least myself for you.

mrbobbytables commented 3 years ago

No action needed, it was more an FYI ping 👍

mrbobbytables commented 3 years ago

/help For cleaning up the owners files. For previous examples of what the clean up PRs look like please see the previous cleanups: https://github.com/kubernetes/org/issues/2013 https://github.com/kubernetes/org/issues/2076

k8s-ci-robot commented 3 years ago

@mrbobbytables: 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](https://github.com/kubernetes/org/issues/2456): >/help >For cleaning up the owners files. >For previous examples of what the clean up PRs look like please see the previous cleanups: >https://github.com/kubernetes/org/issues/2013 >https://github.com/kubernetes/org/issues/2076 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
marpaia commented 3 years ago

Hey, I'm actually working my way back into the release team for 1.21. Can you please leave me in the org for now?

mrbobbytables commented 3 years ago

EDIT: @marpaia I just checked and it doesn't look like you're on the RT for 1.21. 😬 ref: https://github.com/kubernetes/sig-release/blob/master/releases/release-1.21/release-team.md Are you getting involved in some other way?

YouthLab commented 3 years ago

Hi~ @mrbobbytables I'm planning keep working for the DOC-SIG team this new year. Can you please leave me in the org for now, too?

mrbobbytables commented 3 years ago

@YouthLab we prefer to move to remove and re-add when the person becomes active again. Things change rapidly in the project and 1.5years with no activity it's easy to lose track of things. I went ahead on adding @marpaia back because I thought they were a part of the release team and already involved (just not reflected on GitHub yet) - that is ON ME for saying yes before looking into it and have asked for more info.

The long term plan is to eventually automate this process (members being removed won't receive a ping). We updated our community membership guidelines outlining who is defined as inactive and how it is counted. For reference, we use devstats as our means to measure inactivity as it takes into account different types of GitHub actions, not just PRs or issues - but edits, comments and more. A general community notification about this policy was then sent to the k-dev mailing list.

We want to limit access to people that are consistently remain active. Org membership grants permissions to Kubernetes project repos and our CI system. If those privileges aren’t being actively used, we remove them to ensure we don’t have security issues down the road.

Not being a member doesn't mean you can't contribute. Many of our contributions come from non-org members. If you're ramping back up within the project, our org membership process has been streamlined. With a few PRs and two sponsors, we can add you back as a member.

YouthLab commented 3 years ago

@mrbobbytables That is ok. This is reasonable, better for the k8s org. And thank you for your reply with good intentions and patience.:)

chenopis commented 3 years ago

-rest

Hi Bob,

Thanks for the heads up. Feel free to remove me, @chenopis, since I am no longer working on Kubernetes.

Cheers,

--Andrew

Andrew Chen | Program Manager, Research Operations | chenopis@google.com | 650-495-4987

On Mon, Jan 25, 2021 at 5:08 AM Bob Killen notifications@github.com wrote:

This is the list of inactive members https://github.com/kubernetes/community/blob/master/community-membership.md#inactive-members that are slated to be removed from our Github Orgs. They have had no devstats recorded since July 1 2019.

Inactive Members:

Repos with inactive owners: Kubernetes Org

Kubernetes SIGs Org

Kubernetes client Org

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

sladyn98 commented 3 years ago

@mrbobbytables I would like to give this issue a shot, I read the comment on slack by @nikhita about updating the owners files. If yes do let me know if I can begin ?

mrbobbytables commented 3 years ago

@sladyn98 You can, just be sure to reference this post when creating PRs doing so. You can see some of the examples linked in #2013 and #2076.

I would also avoid opening PRs up in kubernetes/kubernetes to start as things are a bit more complicated with owners files there.

One other FYI - if the person being removed was an approver, they should be added as an emeritus_approver.

sladyn98 commented 3 years ago

I opened some PRs for some of the files, I will continue creating pull requests once I know what I am doing is right :)

mrbobbytables commented 3 years ago

@sladyn98 They look good :) It might just take a little bit for them to get reviewed. 👍

nikhita commented 3 years ago

All PRs to clean up OWNERS files have merged. Closing!