From c4715a4029ffd41438dd21e52e2f8a2e10294b34 Mon Sep 17 00:00:00 2001 From: Tim Pepper Date: Fri, 19 Nov 2021 16:22:44 -0800 Subject: [PATCH 01/13] proper noun the applicable committee names 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 --- committee-code-of-conduct/election.md | 28 ++++++++++--------- committee-code-of-conduct/incident-process.md | 4 +-- 2 files changed, 17 insertions(+), 15 deletions(-) diff --git a/committee-code-of-conduct/election.md b/committee-code-of-conduct/election.md index 19f369a520d..08048c70a8a 100644 --- a/committee-code-of-conduct/election.md +++ b/committee-code-of-conduct/election.md @@ -10,8 +10,8 @@ This document outlines the process, for Code of Conduct Committee (CoCC) electio ### Eligibility for voting -* Voting will be done by members of the steering committee. -* A member of the steering committee who is also a nominee for the code of conduct committee is not eligible to vote. +* Voting will be done by members of the Steering Committee. +* A member of the Steering Committee who is also a nominee for the Code of Conduct Committee is not eligible to vote. ### Eligibility for candidacy @@ -25,16 +25,17 @@ This document outlines the process, for Code of Conduct Committee (CoCC) electio ### Election process -The steering committee will announce a request for nominations some time in July from anyone meeting the [eligibility for candidacy](#eligibility-for-candidacy) guidelines. +The Steering Committee will announce a request for nominations some time in July from anyone meeting the [eligibility for candidacy](#eligibility-for-candidacy) guidelines. -The steering committee will accept nominations for at least 1 week. Though the steering -committee may choose to accept nominations for longer. Once the announced nomination +The Steering Committee will accept nominations for at least 1 week. Though the Steering +Committee may choose to accept nominations for longer. Once the announced nomination period ends, steering committee will hold an election using [Elekto](https://elections.k8s.io/) and will publicly announce the results of the election. #### Nomination process Nominations can be collected via any means. In the past a Google form has been used to collect nominations. The form had the following questions which may be used as a template for subsequent elections: + * Email Address (required) * Name of Nominee (required) * Email address of Nominee (required) @@ -44,8 +45,9 @@ Nominations can be collected via any means. In the past a Google form has been u The nomination form must be communicated via email to [Kubernetes dev](https://groups.google.com/forum/#!forum/kubernetes-dev) mailing list. -Prior to the voting process, Steering must: -* Vet that all nominees support the role of the code of conduct committee, i.e. maintaining a safe and inclusive space for everyone to work on Kubernetes. +Prior to the voting process, Steering Committee must: + +* Vet that all nominees support the role of the Code of Conduct Committee i.e., maintaining a safe and inclusive space for everyone to work on Kubernetes. * Confirm with all nominees (that were not self nominations) that they accept the nomination. ### Maximal representation @@ -57,7 +59,7 @@ that limits the number of members employed by the same company to two. Election cycles are scheduled such that roughly half of the seats come up for re-election each year for purposes of continuity. The exact number of seats -alternates between 2 and 3. The elections by the steering committee should be +alternates between 2 and 3. The elections by the Steering Committee should be held and announced before the previous appointments expire (typically in Aug). ### Emeritus Term @@ -68,19 +70,19 @@ lists, historical data, and any other activities related to the CoCC. ### Vacancies -In the event of a resignation or other loss of an elected committee +In the event of a resignation or other loss of an elected CoCC member, the candidate with the next most votes from the previous election will be offered the seat. This process will continue until the seat is filled. In case this fails to fill the seat, a special election for that position will be held as soon as possible. Eligible voters from the most recent election will vote in the special election (ie: eligibility will not be redetermined -at the time of the special election). A committee member elected in a special +at the time of the special election). A CoCC member elected in a special election will serve out the remainder of the term for the person they are replacing, regardless of the length of that remainder. -In the event that the committee votes to dissolve in its entirety an entirely -new special election will be held by the steering committee instead of filling +In the event that the CoCC votes to dissolve in its entirety an entirely +new special election will be held by the Steering Committee instead of filling with names from the previous election. Those elected will complete the remaining -terms of the previous, dissolved, committee. With those receiving the highest +terms of the previous, dissolved CoCC's members. With those receiving the highest votes receiving the longest term. diff --git a/committee-code-of-conduct/incident-process.md b/committee-code-of-conduct/incident-process.md index 007f465211d..527914edb12 100644 --- a/committee-code-of-conduct/incident-process.md +++ b/committee-code-of-conduct/incident-process.md @@ -47,7 +47,7 @@ At times we encourage community members to email us if an incident is ongoing an The Code of Conduct Committee's primary means of contact is our email address, conduct@kubernetes.io. -We can also be reached via Slack direct messages to individual committee members (see [member list](https://github.com/kubernetes/community/tree/master/committee-code-of-conduct#members)) or otherwise, though we might direct you to contact us via email. +We can also be reached via Slack direct messages to individual CoCC members (see [member list](https://github.com/kubernetes/community/tree/master/committee-code-of-conduct#members)) or otherwise, though we might direct you to contact us via email. ### How is the privacy of a report protected? @@ -121,7 +121,7 @@ When deciding how to address an incident, the Code of Conduct Committee follows - Prioritizing education and coaching for those involved, when possible - Prioritizing the protection of contributing members of the Kubernetes project over external parties. This does not mean that we protect people with a higher number of commits or more seniority in the project, however. -In general, the committee strives for unanimous consensus before taking an action. +In general, the CoCC strives for unanimous consensus before taking an action. For example, we may choose to do nothing, to issue a private warning, to offer coaching, to recommend organizational changes, or to ban someone from a community platform. From 02173e6f44ab03f1cbdcfd9e22ec427059087719 Mon Sep 17 00:00:00 2001 From: Tim Pepper Date: Fri, 19 Nov 2021 16:46:55 -0800 Subject: [PATCH 02/13] clarify policy on committee conflict of interest 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 --- committee-code-of-conduct/election.md | 28 +++++++++++++++++++++------ 1 file changed, 22 insertions(+), 6 deletions(-) diff --git a/committee-code-of-conduct/election.md b/committee-code-of-conduct/election.md index 08048c70a8a..2b645fe356a 100644 --- a/committee-code-of-conduct/election.md +++ b/committee-code-of-conduct/election.md @@ -29,7 +29,7 @@ The Steering Committee will announce a request for nominations some time in July The Steering Committee will accept nominations for at least 1 week. Though the Steering Committee may choose to accept nominations for longer. Once the announced nomination -period ends, steering committee will hold an election using [Elekto](https://elections.k8s.io/) +period ends, Steering Committee will hold an election using [Elekto](https://elections.k8s.io/) and will publicly announce the results of the election. #### Nomination process @@ -55,6 +55,20 @@ Prior to the voting process, Steering Committee must: Maximal representation of a single employer is `QUORUM - 1`. With a five person committee, that limits the number of members employed by the same company to two. +### Committee Conflict of Interest + +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. + ### Election Cycles Election cycles are scheduled such that roughly half of the seats come up for @@ -81,8 +95,10 @@ at the time of the special election). A CoCC member elected in a special election will serve out the remainder of the term for the person they are replacing, regardless of the length of that remainder. -In the event that the CoCC votes to dissolve in its entirety an entirely -new special election will be held by the Steering Committee instead of filling -with names from the previous election. Those elected will complete the remaining -terms of the previous, dissolved CoCC's members. With those receiving the highest -votes receiving the longest term. +In the event that the CoCC votes to dissolve in its entirety, a special +election will be held by the Steering Committee (instead of filling with names +from the previous election). Those elected will complete the remaining terms of +the dissolved CoCC. + +Candidates receiving the highest number of votes will receive the longest term +from the seats open for election. From 31d12a7c1b6a022c6109ebe1c0e39724beeaa0bd Mon Sep 17 00:00:00 2001 From: Tim Pepper Date: Fri, 19 Nov 2021 17:15:17 -0800 Subject: [PATCH 03/13] remove historic CoCC bootstrapping process document 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 --- .../bootstrapping-process.md | 36 ------------------- 1 file changed, 36 deletions(-) delete mode 100644 committee-code-of-conduct/bootstrapping-process.md diff --git a/committee-code-of-conduct/bootstrapping-process.md b/committee-code-of-conduct/bootstrapping-process.md deleted file mode 100644 index a98ef9fb71d..00000000000 --- a/committee-code-of-conduct/bootstrapping-process.md +++ /dev/null @@ -1,36 +0,0 @@ -# Bootstrapping Document for Kubernetes Code of Conduct Committee - -This document (created by the Kubernetes Steering Committee) outlines what the Code of Conduct Committee (CoCC) is responsible for, how to create it, and the rough processes for them to get started. - -## Objectives of the CoCC -* Maintain the Code of Conduct (CoC) document and iterate as needed. - * All CoC revisions must be approved by the Steering Committee. - * Currently, we use the CNCF CoC. Any addendums or changes based off learnings in the Kubernetes community should be owned by this body of people, the Kubernetes Code of Conduct Committee (CoCC). -* Determine and make transparent how CoC issues and incidents are reported and handled in the community. -* Enforce the Code of Conduct within the Kubernetes community. - * Discuss with parties affected - * Come up with resolution - * For moderation on a day-to-day basis, work with the existing community-management subproject under SIG Contributor Experience -* Figure out how to keep and then keep a record of CoC reports and outcomes for precedent _This is something we are still actively discussing on how to do and is not fully hardened._ - -## Formation of the Code of Conduct Committee (CoCC): -* The CoCC consists of 5 members. In the first election, the top 3 voted people will be appointed 2 year terms and the other 2 members will be appointed for a 1 year term. - * CoCC members appointed for a 1 year term may be elected again the following year. - * The Steering Committee and SIG Chairs are eligible to nominate people for the Code of Conduct Committee (CoCC). _This may change during the next election._ - * The Steering Committee votes on nominees for the CoCC -* Characteristics and Guidance for nominating people for the CoCC: - * Do not have to be part of the Kubernetes or CNCF community - * Previous experience on an Ethics Committee or Code of Conduct Committee is appreciated - * Has demonstrated integrity, professionalism, and positive influence within the community - * Experience with the tools which we use to communicate (Zoom, Slack, GitHub, etc.) within the Kubernetes community is appreciated - * Is generally a responsible human -* The members of the Code of Conduct Committee (CoCC) will be public so the people who report CoC issues know exactly who they are working with. - -## Upon appointment, the CoCC will: -* Review the current Code of Conduct and propose revisions or addendums if necessary. - * There is already work being done around making the CoC more enforceable, so this work will be carried forward in the CoCC. -* Add an addendum to the CoC with instructions on how to contact the CoCC -* Be briefed on past and current code of conduct issues within the Kubernetes community by people who have been dealing with these issues thus far -* Revisit how code of conduct issues are reported and escalated and ensure these processes are visible and known to the community -* Determine how they envision their process going forward. The Steering Committee will make the recommendation to the Code of Conduct Committee that they have a standing hour long meeting every other week for the first twelve months after they are appointed, but the CoCC can figure out what works for them. -* Propose a method for electing/appointing future members of the committee to the Steering Committee if they choose. From d33972281f47c056cc5da44da175bdd49b098577 Mon Sep 17 00:00:00 2001 From: Stephen Augustus Date: Tue, 15 Aug 2023 18:39:43 -0400 Subject: [PATCH 04/13] elections: Move conflict of interest resolution to separate doc Signed-off-by: Stephen Augustus --- committee-code-of-conduct/election.md | 16 +++------------- elections/committee-conflict-of-interest.md | 13 +++++++++++++ 2 files changed, 16 insertions(+), 13 deletions(-) create mode 100644 elections/committee-conflict-of-interest.md diff --git a/committee-code-of-conduct/election.md b/committee-code-of-conduct/election.md index 2b645fe356a..2b2dcd059de 100644 --- a/committee-code-of-conduct/election.md +++ b/committee-code-of-conduct/election.md @@ -55,19 +55,9 @@ Prior to the voting process, Steering Committee must: Maximal representation of a single employer is `QUORUM - 1`. With a five person committee, that limits the number of members employed by the same company to two. -### Committee Conflict of Interest - -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. +### Committee Conflicts of Interest + +Potential committee conflicts of interest are detailed in the [election documentation](/elections/committee-conflict-of-interest.md). ### Election Cycles diff --git a/elections/committee-conflict-of-interest.md b/elections/committee-conflict-of-interest.md new file mode 100644 index 00000000000..3500ab8bd4d --- /dev/null +++ b/elections/committee-conflict-of-interest.md @@ -0,0 +1,13 @@ +# Committee Conflicts of Interest + +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. From bef9e0995e78b47e6c503b4c235953ad945c4d80 Mon Sep 17 00:00:00 2001 From: Stephen Augustus Date: Tue, 15 Aug 2023 18:57:21 -0400 Subject: [PATCH 05/13] elections: Integrate review feedback on CoI language Signed-off-by: Stephen Augustus --- elections/committee-conflict-of-interest.md | 24 +++++++++++---------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/elections/committee-conflict-of-interest.md b/elections/committee-conflict-of-interest.md index 3500ab8bd4d..b65fb072e64 100644 --- a/elections/committee-conflict-of-interest.md +++ b/elections/committee-conflict-of-interest.md @@ -1,13 +1,15 @@ # Committee Conflicts of Interest -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 serving on +committees in the Kubernetes Community exists with the +[Steering Committee](/committee-steering/README.md) and +the [Code of Conduct Committee](/committee-code-of-conduct/README.md). + +**_Kubernetes Community members cannot serve on both committees simultaneously._** + +Upon appointment, 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. From 211ec62832b94039fb23a50c498d8fc0c2570586 Mon Sep 17 00:00:00 2001 From: Stephen Augustus Date: Tue, 15 Aug 2023 23:13:06 -0400 Subject: [PATCH 06/13] elections: Update conflict of interest resolution timing Co-authored-by: Josh Berkus --- elections/committee-conflict-of-interest.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/elections/committee-conflict-of-interest.md b/elections/committee-conflict-of-interest.md index b65fb072e64..628e18b57f4 100644 --- a/elections/committee-conflict-of-interest.md +++ b/elections/committee-conflict-of-interest.md @@ -7,7 +7,7 @@ the [Code of Conduct Committee](/committee-code-of-conduct/README.md). **_Kubernetes Community members cannot serve on both committees simultaneously._** -Upon appointment, the (Steering Committee) election committee will reach out to +Upon the creation of a potential conflict (after the candidate is nominated for a position that would conflict, and before the conclusion of the election), an uninvolved member of Steering will reach out to them to determine which committee they want to continue with in the event that they are elected. If the active election is for the Steering Committee, the Election Officers will be informed of this decision, and can request that Steering contact the candidate. the newly elected Steering Committee member and ask which committee they intend to continue with. From 8707f29a7cdf379194948c49a14909ff4842df36 Mon Sep 17 00:00:00 2001 From: Stephen Augustus Date: Wed, 16 Aug 2023 12:56:06 -0400 Subject: [PATCH 07/13] elections/coi: Integrate review feedback - Highlight ways in which a conflict may arise - Add timing for conflict resolution Signed-off-by: Stephen Augustus --- elections/committee-conflict-of-interest.md | 32 +++++++++++++++++---- 1 file changed, 26 insertions(+), 6 deletions(-) diff --git a/elections/committee-conflict-of-interest.md b/elections/committee-conflict-of-interest.md index 628e18b57f4..27efc7c6f07 100644 --- a/elections/committee-conflict-of-interest.md +++ b/elections/committee-conflict-of-interest.md @@ -1,15 +1,35 @@ # Committee Conflicts of Interest +## Steering Committee and CoCC + At time of writing, the only known conflict of interest for serving on committees in the Kubernetes Community exists with the [Steering Committee](/committee-steering/README.md) and -the [Code of Conduct Committee](/committee-code-of-conduct/README.md). +the [Code of Conduct Committee (CoCC)](/committee-code-of-conduct/README.md). **_Kubernetes Community members cannot serve on both committees simultaneously._** -Upon the creation of a potential conflict (after the candidate is nominated for a position that would conflict, and before the conclusion of the election), an uninvolved member of Steering will reach out to them to determine which committee they want to continue with in the event that they are elected. If the active election is for the Steering Committee, the Election Officers will be informed of this decision, and can request that Steering contact the candidate. -the newly elected Steering Committee member and ask which committee they intend -to continue with. +This conflict may arise in the following scenarios: + +- A standing Steering Committee member has accepted a nomination to serve on + the Code of Conduct Committee +- A standing CoCC member has elected to run for a seat on the Steering + Committee +- A Kubernetes Community member has been nominated for candidacy for both + committees + +Given the uniqueness of the respective committee charters, their memberships' +position in the community, and the difference in how these committees need to +adjudicate on community matters, _candidates must be able to declare their +preference in which committee they would like to serve on, if elected_. + +After the candidate is nominated for a position that would conflict and before +the conclusion of the first of the two elections to complete, a non-conflicted +Election Officer will reach out to the candidate to determine which committee +they want to continue with in the event that they are elected. + +This process should occur as soon as possible after a potential conflict has +been identified. -The committee where that individual vacated their seat will fill that vacancy -per existing election or committee vacancy rules. +If applicable, the committee where that individual vacated their seat will fill +that vacancy per existing election or committee vacancy rules. From 5c4823d3d75124e58b1999327e4aa017ed206c2c Mon Sep 17 00:00:00 2001 From: Stephen Augustus Date: Wed, 16 Aug 2023 13:09:29 -0400 Subject: [PATCH 08/13] elections/coi: Add section about withdrawing candidates Signed-off-by: Stephen Augustus --- elections/committee-conflict-of-interest.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/elections/committee-conflict-of-interest.md b/elections/committee-conflict-of-interest.md index 27efc7c6f07..ed374998b62 100644 --- a/elections/committee-conflict-of-interest.md +++ b/elections/committee-conflict-of-interest.md @@ -31,5 +31,9 @@ they want to continue with in the event that they are elected. This process should occur as soon as possible after a potential conflict has been identified. +If the candidate is elected in the first election to conclude and that +appointment matches their preference, the candidate will be withdrawn from the +remaining open election. + If applicable, the committee where that individual vacated their seat will fill that vacancy per existing election or committee vacancy rules. From f81d8daea191f41e2c7881ae13f87500c872c527 Mon Sep 17 00:00:00 2001 From: Stephen Augustus Date: Thu, 17 Aug 2023 01:56:11 -0400 Subject: [PATCH 09/13] elections/coi: Handle case when a Steering election is not active Signed-off-by: Stephen Augustus --- elections/committee-conflict-of-interest.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/elections/committee-conflict-of-interest.md b/elections/committee-conflict-of-interest.md index ed374998b62..7838e8aab17 100644 --- a/elections/committee-conflict-of-interest.md +++ b/elections/committee-conflict-of-interest.md @@ -1,6 +1,6 @@ # Committee Conflicts of Interest -## Steering Committee and CoCC +## Steering Committee and Code of Conduct Committee At time of writing, the only known conflict of interest for serving on committees in the Kubernetes Community exists with the @@ -25,8 +25,10 @@ preference in which committee they would like to serve on, if elected_. After the candidate is nominated for a position that would conflict and before the conclusion of the first of the two elections to complete, a non-conflicted -Election Officer will reach out to the candidate to determine which committee -they want to continue with in the event that they are elected. +Election Officer or in the event that a Steering Committee election is not +active, a non-conflicted Steering Committee member will reach out to the +candidate to determine which committee they want to continue with in the event +that they are elected. This process should occur as soon as possible after a potential conflict has been identified. From 25ef6e6e3c6c1760ec1e3bc06af33973740beee5 Mon Sep 17 00:00:00 2001 From: Stephen Augustus Date: Thu, 17 Aug 2023 02:56:39 -0400 Subject: [PATCH 10/13] elections/coi: Limit the amount of conflicts that occur in a cycle Signed-off-by: Stephen Augustus --- elections/committee-conflict-of-interest.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/elections/committee-conflict-of-interest.md b/elections/committee-conflict-of-interest.md index 7838e8aab17..e75762da3de 100644 --- a/elections/committee-conflict-of-interest.md +++ b/elections/committee-conflict-of-interest.md @@ -39,3 +39,9 @@ remaining open election. If applicable, the committee where that individual vacated their seat will fill that vacancy per existing election or committee vacancy rules. + +In the event that multiple candidates trigger this conflict in an election +cycle, the two (2) affected candidates receiving the most votes will have their +preference honored. In the event that the first election to conclude has only +two seats under consideration, only the affected candidate with the most votes +will have their preference honored. From 2c42bb15aa756f592c28b1530623be457438bf9a Mon Sep 17 00:00:00 2001 From: Stephen Augustus Date: Fri, 18 Aug 2023 08:33:04 -0400 Subject: [PATCH 11/13] elections/coi: Opt for candidacy rules to mitigate potential conflicts Signed-off-by: Stephen Augustus --- elections/committee-conflict-of-interest.md | 68 ++++++++++++--------- 1 file changed, 39 insertions(+), 29 deletions(-) diff --git a/elections/committee-conflict-of-interest.md b/elections/committee-conflict-of-interest.md index e75762da3de..088d00023a5 100644 --- a/elections/committee-conflict-of-interest.md +++ b/elections/committee-conflict-of-interest.md @@ -1,12 +1,12 @@ # Committee Conflicts of Interest -## Steering Committee and Code of Conduct Committee - At time of writing, the only known conflict of interest for serving on committees in the Kubernetes Community exists with the [Steering Committee](/committee-steering/README.md) and the [Code of Conduct Committee (CoCC)](/committee-code-of-conduct/README.md). +## Steering Committee and Code of Conduct Committee + **_Kubernetes Community members cannot serve on both committees simultaneously._** This conflict may arise in the following scenarios: @@ -18,30 +18,40 @@ This conflict may arise in the following scenarios: - A Kubernetes Community member has been nominated for candidacy for both committees -Given the uniqueness of the respective committee charters, their memberships' -position in the community, and the difference in how these committees need to -adjudicate on community matters, _candidates must be able to declare their -preference in which committee they would like to serve on, if elected_. - -After the candidate is nominated for a position that would conflict and before -the conclusion of the first of the two elections to complete, a non-conflicted -Election Officer or in the event that a Steering Committee election is not -active, a non-conflicted Steering Committee member will reach out to the -candidate to determine which committee they want to continue with in the event -that they are elected. - -This process should occur as soon as possible after a potential conflict has -been identified. - -If the candidate is elected in the first election to conclude and that -appointment matches their preference, the candidate will be withdrawn from the -remaining open election. - -If applicable, the committee where that individual vacated their seat will fill -that vacancy per existing election or committee vacancy rules. - -In the event that multiple candidates trigger this conflict in an election -cycle, the two (2) affected candidates receiving the most votes will have their -preference honored. In the event that the first election to conclude has only -two seats under consideration, only the affected candidate with the most votes -will have their preference honored. +There are several factors under consideration when formulating a reasonable +process for resolving this conflict of interest: + +- The distinctness of the Steering and CoCC charters, not limited to how these + committees need to adjudicate on community matters +- The Kubernetes Community's expectation of commitment in its committee members + for duration of their terms +- Continuity of committees and the duties they discharge +- Undue burden on existing committee members to balance workload through + committee membership transitions, not limited to onboarding/offboarding +- Undue burden on Election Officers in supporting overlapping elections with + the potential to generate conflicts +- Minimization of conflict of interest edge cases not otherwise described by + this document + +With these considerations in mind, the following rules exist to prevent or +resolve membership conflicts of interest between Steering and the CoCC: + + + +- Loss of committee member that occurs due to this conflict of interest will + be resolved per existing election or committee vacancy rules +- Candidates who are nominated for a seat on both Steering and CoCC within the + same 12-month period must: + - (if elected) accept a seat on the committee whose election concludes first + - be withdrawn from candidacy in second election to conclude +- Standing Steering or CoCC members must have served on their committee for a + period of twelve (12) months to be considered eligible for candidacy in the + other committee's election +- Kubernetes Community members who have recently vacated a seat on either + Steering or CoCC will be ineligible for candidacy for a period of three (3) + months + +Should this conflict of interest arise in a manner that cannot be resolved by +these rules, a non-conflicted Election Officer or, in the event that a Steering +Committee election is not active, a non-conflicted Steering Committee member +will reach out to the candidate to discuss resolution. From 485758fe0e1e29de67aac53b166cb01a844d9b08 Mon Sep 17 00:00:00 2001 From: Stephen Augustus Date: Fri, 18 Aug 2023 09:07:52 -0400 Subject: [PATCH 12/13] elections/coi: Clarify that voluntarily vacation will be subject to eligibility cooldown Co-authored-by: Kat Cosgrove --- elections/committee-conflict-of-interest.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/elections/committee-conflict-of-interest.md b/elections/committee-conflict-of-interest.md index 088d00023a5..00f23a71928 100644 --- a/elections/committee-conflict-of-interest.md +++ b/elections/committee-conflict-of-interest.md @@ -47,8 +47,8 @@ resolve membership conflicts of interest between Steering and the CoCC: - Standing Steering or CoCC members must have served on their committee for a period of twelve (12) months to be considered eligible for candidacy in the other committee's election -- Kubernetes Community members who have recently vacated a seat on either - Steering or CoCC will be ineligible for candidacy for a period of three (3) +- Kubernetes Community members who have recently voluntarily vacated a seat on either + Steering or CoCC without serving the complete term will be ineligible for candidacy for a period of three (3) months Should this conflict of interest arise in a manner that cannot be resolved by From c36f60df2a6d25519a87118853065720f1e30415 Mon Sep 17 00:00:00 2001 From: Stephen Augustus Date: Fri, 18 Aug 2023 11:53:35 -0400 Subject: [PATCH 13/13] elections/coi: Add document effective date Signed-off-by: Stephen Augustus --- elections/committee-conflict-of-interest.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/elections/committee-conflict-of-interest.md b/elections/committee-conflict-of-interest.md index 00f23a71928..0afb33f90c5 100644 --- a/elections/committee-conflict-of-interest.md +++ b/elections/committee-conflict-of-interest.md @@ -1,5 +1,9 @@ # Committee Conflicts of Interest +**Effective date**: 2023-10-03 (following the announcement of the [2023 Steering Committee election][steering-2023-election-schedule] results) + +[steering-2023-election-schedule]: /elections/steering/2023/README.md#schedule + At time of writing, the only known conflict of interest for serving on committees in the Kubernetes Community exists with the [Steering Committee](/committee-steering/README.md) and