-
Notifications
You must be signed in to change notification settings - Fork 36
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
update OWNERS #67
Comments
Or maybe some of the slack-admins can chip in? |
Lordy, yes. OWNERS should be:
|
gentle nudge @nikhita @jeefy @kubernetes-sigs/sig-contributor-experience-leads cc proposed owners (per josh above) @jberkus @mrbobbytables @coderanger @cpanato @kubernetes-sigs/sig-contributor-experience-leads @upodroid @ameukam @dims (and me) |
+1 |
I didn't realize I hadn’t responded here—apologies for the delay! Please feel free to remove me (and any other inactive owners). I think it’s best to update the list to include only those who can review and approve in a timely manner, rather than waiting on inactive folks. Of course, we can always re-add people later if they’d like to contribute again. |
Hi folks, please ACK to confirm if you're willing to own this and will actively review/approve this repo: And we'll get an OWNERS PR going ... (I assume at least @cpanato, and I'm willing to help and I think this is important) |
Not willing to own this. Sorry. |
I have been meaning to poke at what we have, so happy to review/approve |
Happy to review/approve and help with the infra side of things |
ack |
Ack and +1 |
ack |
Ack. I can help review/approve. Thanks! |
At least two of the four listed OWNERS are inactive in the organization
cc @nikhita @jeefy @kubernetes-sigs/sig-contributor-experience-leads
this repo is running critical infra but PRs are sitting unresponded, images are not getting promoted (#66) or deployed (#56) and probably have alarming CVEs (seeing as they're years old since the last builds and serving webhooks)
Can we add some active owners and clean this up?
I can spare a little time to help out here, I do not want to see a compromise for this infra and I've been working on getting everything migrated to the community at least.
The text was updated successfully, but these errors were encountered: