kubernetes
Committee Conflict of Interest resolution
This is a carry of @tpepper's https://github.com/kubernetes/community/pull/6243 / https://github.com/kubernetes/steering/pull/224.
~I still need to sweep the comment/review history from the previous PRs and resolve open concerns, but getting this up ASAP as a point for discussion (as election cycles are already underway).~
Part of https://github.com/kubernetes/steering/issues/221
cc: @kubernetes/steering-committee @jberkus
@justaugustus: GitHub didn't allow me to request PR reviews from the following users: kubernetes/code-of-conduct-committee, kubernetes/steering-committee.
Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.
In response to this:
Ready for review.
Committee members: /cc @kubernetes/steering-committee @kubernetes/code-of-conduct-committee
Election subproject: /cc @jberkus @parispittman @mrbobbytables @nikhita @fsmunoz /retitle Committee Conflict of Interest resolution /hold
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/test-infra repository.
Added a section about withdrawing the candidate from the second election to complete in https://github.com/kubernetes/community/pull/7468/commits/b7fd89e0bd8e4dd04af21575170162b44c601627.
Maybe I'm missing some nuance, but if terms for both positions are two years and elections run at different times, I suggest that a candidate is no longer eligible to run in an election for a committee position they do not currently hold if they have won their existing position within the last 12 months. This minimizes the opportunity for conflict, as well as the burden on the community and whichever committee is temporarily disadvantaged by a seat being vacated early.
Example A: Candidate runs for and wins a seat on the CoCC. A few months later, nominations for Steering open. As the candidate won their CoCC seat less than one year ago, they are ineligible to run for Steering.
Example B: Candidate runs for and wins a seat on the CoCC. A year and some change into their term, nominations open for Steering. As the candidate has served more than 12 months on the CoCC, they are eligible to run for Steering. No conflict exists until they win the seat on Steering; if they win, the seat on the CoCC must be vacated, and a special election is triggered for the now-vacant CoCC seat.
Example C: Candidate runs for a seat on the CoCC, but is not successful. They do not currently hold a committee position, so they are eligible to run for Steering that same election year.
It is possible for a candidate holding a seat to willingly vacate their existing position in order to shortcut the 12-month lockout period. For that reason, I also suggest a 3-6 month lockout from running in any election in the case of a seat being vacated voluntarily. If a candidate is experiencing issues in their personal or professional life that prevent them from fulfilling their duties to the Committee rather than vacating the seat simply to get around the lockout period, those issues are unlikely to be resolved in a short period of time.
TL;DR: You shouldn't be able to run for two elections in the same 12-month period if you won the first one.
In both this and the above question, my personal opinion is that we should not seek to restrict the opportunities for Kubernetes Community members to run for committee membership outside of what is detailed in the "Eligibility for candidacy" sections of each committee's election process.
+1 to what @justaugustus said. The concerns about candidates running for multiple committees at different points in time should be addressed in the "Eligibility for Candidacy" sections, for example, a sitting committee member running for another committee.
Overall +1, the one caveat that these should go in effect after our current round of elections conclude as they were not in place before either election was started.
Overall +1, the one caveat that these should go in effect after our current round of elections conclude as they were not in place before either election was started.
@mrbobbytables -- Could we instead set an effective date on the top of the doc for Monday, October 2 (Public announcement of Results at Public Steering Committee Meeting)? ref: https://github.com/kubernetes/community/tree/master/elections/steering/2023#schedule
This issue has been around for two years and it would be great to not leave this languishing for much longer. 📿
Oh yeah, I'm fine with that - I was good with merging beforehand without a date in the doc as long as there was a general understanding they'd go in effect after this round of elections.
@mrbobbytables -- okay, perfect. Added an effective date of 2023-10-03 (a day after the election results are announced).
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cpanato, justaugustus, katcosgrove, palnabarun
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~committee-code-of-conduct/OWNERS~~ [cpanato,justaugustus,palnabarun]
- ~~elections/OWNERS~~ [cpanato,justaugustus,palnabarun]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
PR needs rebase.
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/test-infra repository.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle rotten - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Reopen this PR with
/reopen - Mark this PR as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closed this PR.
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closedYou can:
- Reopen this PR with
/reopen- Mark this PR as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
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/test-infra repository.