8000 Clarify policies for removal of steering committee members by evankanderson · Pull Request #1688 · knative/community · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Clarify policies for removal of steering committee members #1688

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

Merged
merged 3 commits into from
Jun 10, 2025

Conversation

evankanderson
Copy link
Member
@evankanderson evankanderson commented May 28, 2025

Changes

  • Documents the expectation that steering committee members remain active.
  • Documents the process for removing a steering committee member, either due to inactivity, or for cause.
  • Clears up an ambiguous section which defined a second way of filling a KSC vacancy. (Oops!)
  • Update meeting cadence to match current practice.
  • Remove explanatory detail on 2024 SC composition which no longer applies.

/kind governance
Fixes #1687

Note that this is purely to address feedback from the governance review, and mostly just clarifies rules that we'd make up on the spot (using the charter approval process) if we needed them.

8000
Update ROLES.md to mention CNCF maintainer status for WG leads.
Run prettier on ROLES.md
Copy link
knative-prow bot commented May 28, 2025

@evankanderson: The label(s) kind/governance cannot be applied, because the repository doesn't have them.

In response to this:

Changes

  • Documents the expectation that steering committee members remain active.
  • Documents the process for removing a steering committee member, either due to inactivity, or for cause.
  • Clears up an ambiguous section which defined a second way of filling a KSC vacancy. (Oops!)

/kind governance
Fixes #1687

Note that this is purely to address feedback from the governance review, and mostly just clarifies rules that we'd make up on the spot (using the charter approval process) if we needed them.

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-sigs/prow repository.

@knative-prow knative-prow bot requested review from dprotaso and nrrso May 28, 2025 17:23
@knative-prow knative-prow bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels May 28, 2025
@knative-prow knative-prow bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels May 28, 2025
@evankanderson
Copy link
Member Author

/hold

This is a charter amendment, so will need some vote.

@knative-prow knative-prow bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 28, 2025
@aliok
Copy link
Member
aliok commented May 29, 2025

/lgtm
/approve

Thanks Evan!

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label May 29, 2025
Copy link
knative-prow bot commented May 29, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aliok, evankanderson

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:
  • OWNERS [aliok,evankanderson]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@evankanderson
Copy link
Member Author

For reference, for non-Steering roles, we offer a fairly generous 12-month inactivity window:

https://github.com/knative/community/blob/main/ROLES.md#inactivity

I think a shorter window for Steering makes sense given the requirements for quorum votes which none of the other roles have.

@dprotaso
Copy link
Member

+1 from me

we have quorum
/hold cancel

cc @matzew

@knative-prow knative-prow bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 10, 2025
@knative-prow knative-prow bot merged commit ff5f7f1 into knative:main Jun 10, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Governance - Add requirements for remaining a KSC member / removing a KSC member
3 participants
0