-
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
Follow on working group gov #2814
Conversation
cc @jdumars |
cc @kubernetes/steering-committee |
One nit: "do not own code" should be "do not own code inside kubernetes/kubernetes or other core repositories" I think that addresses some of the concerns from the prior PR. Thank you for getting this wrapped up! |
/lgtm |
/lgtm |
@@ -62,8 +60,7 @@ requirements for that are: | |||
- chair information | |||
- meeting information | |||
- contact methods | |||
- any sig stakeholders | |||
- any subproject stakeholders | |||
- any [sig or subproject](sig-governance.md#project-management) stakeholders |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dare I ask why sig or subproject? asking from a perspective of wanting to update sigs.yaml
to have working groups specify which entities they interface with
I had assumed it was just going to be a sigs:
field, now I'm guessing it would look like sigs:
and subprojects:
fields and wondering why the additional complexity
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(ref #2176)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to this question
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PTAL. I removed the line about projects.
@@ -92,7 +89,7 @@ Working Groups will be disbanded if either of the following is true: | |||
- Zoom | |||
|
|||
The current Chair may step down at any time. When they do so, a new Chair may be selected through lazy consensus | |||
within the Working Group. | |||
within the Working Group, and [sigs.yaml](../../sigs.yaml) should be updated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
markdown nit: (/sigs.yaml)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall /lgtm
@@ -62,8 +60,7 @@ requirements for that are: | |||
- chair information | |||
- meeting information | |||
- contact methods | |||
- any sig stakeholders | |||
- any subproject stakeholders | |||
- any [sig or subproject](sig-governance.md#project-management) stakeholders |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to this question
915dc73
to
bdc2317
Compare
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/lgtm |
/lgtm Ship it! We should aim to have tweaks/refactors like this merge quickly. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: philips The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
No description provided.