Skip to content
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

Open
parispittman opened this issue Oct 18, 2021 · 4 comments
Open

GB Rep term should match SC terms #218

parispittman opened this issue Oct 18, 2021 · 4 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@parispittman
Copy link
Contributor

parispittman commented Oct 18, 2021

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

  • one option: make terms 1 or 3 years to catch up with the cycles but in my experience, 3 years is too long and 1 year is not long enough since the group only meets 2-3x a year as it is which is hard for making change.
  • second option: have an alternate that is on a different term schedule than the elected person; 1 year active and then 1 year as alternate - provides an onboarding path and then at least 3 meetings champion

Open Questions

  • should they be concurrent?
  • what's the process for electing someone?

Next Steps

  • new steering body should debate and discuss
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 9, 2022
@mrbobbytables
Copy link
Member

/remove-lifecycle stale
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 9, 2022
@parispittman
Copy link
Contributor Author

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.

@BenTheElder
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

5 participants