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
updated the OWNERS file to reflect ownership of k/klog #222
Comments
/priority important-longterm |
We recently reviewed this as part of the SIG Instrumentation annual report. We noted subproject owners as @dims @thockin and @DirectXMan12 and we added @dims to the SIG Instrumentation roster. We have an agenda item this week to discuss forming a logging WG. Perhaps we can discuss this further then. https://docs.google.com/document/d/1FE4AQ8B49fYbKhfg4Tx0cui1V0eI4o3PxoqQPUwNEiU/edit#heading=h.cx8m0c4qz1jr |
/lifecycle frozen |
@ehashman given what's in OWNERS now https://github.com/kubernetes/klog/blob/main/OWNERS what do you want to do here? i am happy to close it. |
Are we sure everyone listed in OWNERS is still active and will respond to review resp. approve requests? |
@dims given who's in the OWNERS file now, many of whom have gone emeritus, we think this is still relevant. @serathius will run your maintainers script to update the list. |
Done #309 |
/close |
@ehashman: Closing this issue. In response to this:
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. |
Describe the solution you'd like
when k/klog was originally created (as a fork of glog) the project was owned by SIG Arch, but later it was stated that this should be owned by SIG Instrumentation. klog is listed as a sub-project SIG instrumentation:
https://github.com/kubernetes/community/tree/master/sig-instrumentation#klog
but the OWNER file in this repository does not reflect the owning SIG and contains a list of volunteers, who are mostly inactive here:
https://github.com/kubernetes/klog/blob/master/OWNERS
it feels like it should be updated with SIG Instrumentation members that can monitory changes closely, especially such that are breaking.
/assign @dims @ehashman
/kind cleanup
@kubernetes/sig-instrumentation-members
The text was updated successfully, but these errors were encountered: