-
Notifications
You must be signed in to change notification settings - Fork 63
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
GB Rep term should match SC terms #218
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
spoke about second option with adding an alternative that is on a different term cycle at the last Steering Committee meeting http://bit.ly/k8s-steering-wd @caniszczyk - what's our next step with adding an alt to the k8s rep GB role? steering is in favor of adding. |
cc @cblecker I think currently what we've resolved to instead is to make sure we have steering + GB rep communication channels and are relatively OK with the non-aligned terms. |
Problem Statement
GB rep is 2 years, Steering rep is 2 years but they are not concurrent. It would be a smoother process if they were concurrent with the person elected to GBs Steering term. If they are not, the person will have ~1 year where they need to make sure they link up with steering, ask to be fit into the agenda, etc; whereas, they would already be in those meetings if they still sat on Steering.
We also include emeritus members in the process for GB which in my experience would also be hard because that person would need to be extremely active in the community still.
Proposed Solution
Open Questions
Next Steps
The text was updated successfully, but these errors were encountered: