Steering/CoCC Conflict Resolution #6243
Conversation
For clarity, most of our docs refer to our project committee instances as proper nouns. The Kubernetes Steering Committee is the specific instance of steering committee referenced in the Kubernetes Code of Conduct Committee (CoCC) election document. Signed-off-by: Tim Pepper <tpepper@vmware.com>
We have a known instance of committee conflict of interest with Code of Conduct Committee members being elected to the Steering Committee. Based on these bodies charter, membership is mutually exclusive. But it has not been clearly documented that in such cases one must choose vacate their membership in one body or the other, or how the vacancy would be filled. This clarifying text documents our established practice. (Also present are couple other minor grammar clarifications) Signed-off-by: Tim Pepper <tpepper@vmware.com>
This document has useful historical context, but may cause reader confusion relative to the enacted state of the CoCC now that we are well past boostrapping that committee. Most, if not all, of the information in this document is reflected in other documents which are curated for accuracy. It will remain in the git history for posterity. Signed-off-by: Tim Pepper <tpepper@vmware.com>
k8s-ci-robot
added
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tpepper 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 |
k8s-ci-robot
added
the
approved
|
/hold |
k8s-ci-robot
added
the
do-not-merge/hold
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
/lgtm |
| As project committees have unique charters, there is a possibility | ||
| for a conflict of interest to arise. While multiple scenarios may | ||
| be possible now or in the future, one known example of such conflict | ||
| of interest is where a member of the Code of Conduct Committee is | ||
| elected to the Steering Committee. | ||
|
|
||
| Such conflict will be resolved by the applicable election committee | ||
| reaching out to the newly-elected member and facilitating a decision | ||
| regarding on which committee the individual will continue. The | ||
| committee where that individual vacated their seat will fill that | ||
| vacancy as per existing election or committee vacancy rules. |
There was a problem hiding this comment.
| As project committees have unique charters, there is a possibility | |
| for a conflict of interest to arise. While multiple scenarios may | |
| be possible now or in the future, one known example of such conflict | |
| of interest is where a member of the Code of Conduct Committee is | |
| elected to the Steering Committee. | |
| Such conflict will be resolved by the applicable election committee | |
| reaching out to the newly-elected member and facilitating a decision | |
| regarding on which committee the individual will continue. The | |
| committee where that individual vacated their seat will fill that | |
| vacancy as per existing election or committee vacancy rules. | |
| At time of writing, the only known conflict of interest for Code of Conduct Committee | |
| members and appointees is nomination to the Steering Committee. | |
| Members should not serve on both committees simultaneously. | |
| Upon nomination, the (Steering Committee) election committee will reach out to | |
| the newly elected Steering Committee member and ask which committee they intend to continue with. | |
| The committee where that individual vacated their seat will fill that | |
| vacancy per existing election or committee vacancy rules. |
There was a problem hiding this comment.
"Upon nomination, the (Steering Committee) election committee will each out to"
assuming reach instead of each^^:;;
There was a problem hiding this comment.
Members should not serve on both committees simultaneously reads too weak for me with "should".
|
/lgtm |
There was a problem hiding this comment.
Would be cool to be able to say, "This is how we handle elections for committees and here are some general rules that should be followed"
We now have two PRs (this one and kubernetes/steering#224) that have similar guidance, but different reviews. This is going to lead/is already leading to drift.
What about:
- distilling the guidance for handling membership conflicts here: https://github.com/kubernetes/community/tree/master/events/elections, and then:
- linking that to:
committee-code-of-conduct/election.md, and:- https://github.com/kubernetes/steering/blob/main/elections.md
?
/hold
Agree. We'll need to do more though than distill conflict guidance into https://github.com/kubernetes/community/tree/master/events/elections as that document is currently focused on just Steering Committee elections, ie: "This document is a guide for Election Committee members conducting a Kubernetes Steering Committee Election." |
|
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 |
k8s-ci-robot
added
the
lifecycle/stale
|
The Kubernetes project currently lacks enough active 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 rotten |
k8s-ci-robot
added
lifecycle/rotten
|
The Kubernetes project currently lacks enough active 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. /close |
|
@k8s-triage-robot: Closed this PR. In response to this:
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. |
We have a known conflict of interest potential across Steering and Code of Conduct Committee. This PR documents our current practice for resolving this and does a few other bits of cleanup on docs.
Fixes: kubernetes/steering#221