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
charter: Add changes and election vacancies sections #249
Conversation
Signed-off-by: Stephen Augustus <foo@auggie.dev>
This is roughly a no-op, so the changes process should not apply here. |
/hold for other reviewers and approvers /approve |
I personally agree this is a no-op. However I think you should count this as part of the other change for the purpose of following the change policy, which does not make an exception for no-op changes. |
lgtm |
I also read this as a noop and explicitly states and links current policy and practices. 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.
I also believe this is a no-op. I understand the hesitation with current policy not explicitly calling out no-ops but I think this is reasonable. IMO a good follow-up would be to amend the change policy to account for this in the future.
lgtm
Co-authored-by: Stephen Augustus <foo@auggie.dev>
22469a4
to
2bfc358
Compare
@kubernetes/steering-committee -- Reviews have been addressed and we all seem to be in agreement about this being a no-op. Just needs another LGTM. |
/lgtm |
/hold |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, justaugustus 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 |
LGTM |
lgtm |
lgtm here and in the meeting |
/hold cancel |
(Voted in today's meeting and 7/7 in favor of merging this) |
@@ -127,19 +127,7 @@ History of election officers: | |||
|
|||
### Vacancies | |||
|
|||
In the event of a resignation or other loss of a [bootstrap committee member], | |||
the position will not be refilled. |
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.
what was the rationale earlier for why it will not be filled ?
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.
The bootstrap committee was 12 (13?) seats (extra big to be extra sure about initial set of decisions) and the goal was to get it down to 7 via attrition.
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.
Lol
was to get it down to 7 via attrition.
These commits were peeled off of #248, initially committed by @parispittman:
Co-authored-by: Stephen Augustus foo@auggie.dev
There are no content changes, outside of fixing up links and referencing existing process/procedure.
cc: @kubernetes/steering-committee