Cleanup Kubernetes GitHub organizations - Jan 2024 #4726
Comments
palnabarun
added
the
area/github-membership
|
I received an email and noticed that I am on this to-be-cleaned-up list. I just became a Kubernetes member New membership for Ithrael on January 18, 2024 , and upon reviewing the devstats for the past year, I have made some contributions as well. |
|
@Ithrael -- thanks for the comment and your observations. Rechecked the data. The error was due to how GitHub handles uppercase in usernames and an error in the GitHub org manifest. I have removed your name from the list as well as fixed the error. |
|
hello ✋🏽 i work on Etcd now, Is this a reason not be removed ? |
|
I think we should make an exception for people who have passed on. I understand the principle of least privilege, but it feels disrespectful to remove them. krisnova, carolynvs, thecrudge, Pensu are four of them on there. May their memories continue to be a blessing 🖤 |
|
I agree with @IanColdwater. Is there not a way to address security concerns with a |
|
We can't make them org members and restrict access. While it may not seem the best, we have to prioritize the org. We can't add them to a specialty org or anything either because they must accept joining =/ |
|
Would it be possible to add the usernames in a config file somewhere that would block abilities to run tests and other security measures without removing from the organization? I thought we discussed trying to preserve digital footprint during Steering in November 2019 when Brad Childs passed. I no longer have access to those notes. He is still in the organization: https://github.com/childsb |
|
@parispittman that was likely before we put the policy in place regarding org cleanup. There is no good way to keep them in org without significant effort in prow. IMO - I'd add a page on k8s.dev for memorials and can link out to the individual cncf memorial pages, or have a note somewhere discoverable. |
|
If we decide memorial pages on K8s.dev is the way we want to move forward, I'm happy to do that work. I see more advantages to hosting them on K8s.dev than GitHub. But, first iteration could be links to those cncf/memorial pages. |
|
We should absolutely under no circumstances fail to understand that kubernetes is project for people by people. The contributors are k8s in many ways. A memorial pages for our departed friends is in my opinion a perfect way to enshrine that ideology. |
|
Is it still too late to submit a few PRs or Issues now? |
|
I would like to remain a member please; I contributed to the Certified Kubernetes Conformance Program around the launch, and was recently appointed to the CNCF Governing Board as an alternate. Planning to step up my contributions in the k8s project this year. |
|
@xianlubird @WilliamDenniss The exception period was more for people that have been active in other ways that we could not capture via DevStats. For those that it doesn't apply to, we prefer that people re-apply for org membership after demonstrating consistent activity. |
|
thanks @Elbehery, will make sure it gets updated 👍 |
|
Hey @Elbehery, thanks for noting down your contributions to etcd. I have updated the list to remove your name. When we initially generated the list, we took into cognizance etcd org members as contributors. Since etcd org migration to Kubernetes org machinery is in flux, there are some corner cases. |
|
Hello Could you add my name in the list again? |
|
Hi @KentaTada, you can always file a membership request to request to be added to the org citing your contributions. However, to assure you, not having an org membership shouldn't block you from the issue that you mentioned. |
An org membership grants one access to an elevated set of permissions, and many members also grow to be owners of code. Being inactive for a long period of time impacts the project. We have a policy for defining who is an inactive member. In the past, we have periodically cleaned up inactive members from our several GitHub organizations.
Last year, we made some amendments to our guidelines for inactivity, notably reducing the period for measurement of inactivity to 12 months.
Previous Instances of cleanup: #2456, #2076
If you find yourself in the below list and contribute actively in an area not captured by Devstats, please comment here with details about your contributions. The deadline for exceptions is February 12, 2024. If you miss raising an exception, one can initiate a revert of their removal from the repo.
Following is the list of inactive members who are slated to be removed from the Kubernetes GitHub organizations:
Tasks
The text was updated successfully, but these errors were encountered: