REQUEST: Archive repo kubernetes-sigs/hierarchical-namespaces
enj opened this issue · 5 comments
Repository to archive
kubernetes-sigs/hierarchical-namespaces
Repository and/or sig subproject owners that are approving this archival
@kubernetes/sig-auth-leads
When should this be done
Anytime
Additional context for request
Per the Feb 26, 2025 SIG Auth meeting (agenda, recording), we made the decision to archive the hierarchical-namespaces project due to a lack of maintainers and adopters.
cc @kubernetes/sig-auth-leads @micahhausler @aramase @adrianludwin @rjbez17 @srampal @tashimi
I don't know anything about Kubernetes or hierarchical-namespaces, but it's @rjbez17 that has been the most active in the repository lately as far as I've seen.
Right now he is taking care of some family emergency (kubernetes-sigs/hierarchical-namespaces#408 (comment)), so I suggest giving him some time to respond to this.
And I assume it will be difficult to make releases out of archived repositories, so I would appreciate if you could archive the repository after the next release (which was planned "soon" when the family emergency happened: kubernetes-sigs/hierarchical-namespaces#408 (comment)).
I suggest giving him some time to respond to this
We have already contacted Ryan and the other maintainers in private before opening this issue. He is aware and supportive of our decision to archive the repo. The same is true for Adrian.
And I assume it will be difficult to make releases out of archived repositories
Anyone is free to fork the repo to build artifacts as desired.
I would appreciate if you could archive the repository after the next release
Per kubernetes-sigs/hierarchical-namespaces#402 it is no longer possible to push new images for HNC, and I would prefer not burden Ryan or anyone else with unnecessary work.
I ultimately agree with the decision here. I’ve clearly not done a good enough job maintaining this the last few years and for that I apologize. I’ve had more than a few people saying they’ll help without any follow up. @pjonsson if you are willing to sign up for long term maintenance help (you've already helped quite a bit recently, but I know this isn't really your area of expertise) we can think about reconsidering? While looking at what was required to cut a new patch release I quickly realized it was not going to be possible with no one available to approve my PRs as I am currently the only maintainer.
I've never had the luxury of contributing to projects as part of my day job, I've always been 100% volunteering on my own time. Unfortunately my day job and family life have not allowed me as much time as I've had in the past. I would love to keep this project alive and can continue to dedicate some time to it but not without dedicated help.
@rjbez17 - I’ve never been involved in maintaining a project, but I’d be willing to give it a shot. We use HNC heavily at my company and it would be a shame to see this project go away.