-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Rationalize governance.md, sig-governance.md and committee-steering/governance #1997
Comments
/committee steering |
What do y'all think about moving all of this into /governance/*? |
SGTM. The docs in committee-steering aren't very discoverable, I've found. Originally the content of sig-governance.md (and some of the other docs, like community-membership.md) were all in governance.md, and then were broken out. Now more content is being added to governance.md. |
@jbeda That SGTM. I am OOO through Wednesday so don't block on me. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/assign I'm working on this |
What's remaining here? Paris solved most of this in #3287 🚀 We have both https://github.com/kubernetes/community/blob/master/governance.md and {sig,wg,ug}-governance in https://github.com/kubernetes/community/tree/master/committee-steering/governance today but I see the former as describing what each community group means and I'm not sure if they need to be de-duplicated? 🤔 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/close @jbeda - it looks like we addressed this but happy to hear other suggestions if you feel like it doesn't satisfy this issue. |
@parispittman: 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. |
There is a lot of overlap across these.
@kubernetes/steering-committee
See also #1986 and #1994.
The text was updated successfully, but these errors were encountered: