Skip to content

Commit 152db13

Browse files
committed
elections: Integrate review feedback on CoI language
Signed-off-by: Stephen Augustus <[email protected]>
1 parent f999401 commit 152db13

File tree

1 file changed

+13
-11
lines changed

1 file changed

+13
-11
lines changed
Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,15 @@
11
# Committee Conflict of Interest
22

3-
As project committees have unique charters, there is a possibility
4-
for a conflict of interest to arise. While multiple scenarios may
5-
be possible now or in the future, one known example of such conflict
6-
of interest is where a member of the Code of Conduct Committee is
7-
elected to the Steering Committee.
8-
9-
Such conflict will be resolved by the applicable Election Committee
10-
reaching out to the newly-elected member and facilitating a decision
11-
regarding on which committee the individual will continue. The
12-
committee where that individual vacated their seat will fill that
13-
vacancy as per existing election or committee vacancy rules.
3+
At time of writing, the only known conflict of interest for serving on
4+
committees in the Kubernetes Community exists with the
5+
[Steering Committee](/committee-steering/README.md) and
6+
the [Code of Conduct Committee](/committee-code-of-conduct/README.md).
7+
8+
**_Kubernetes Community members cannot serve on both committees simultaneously._**
9+
10+
Upon appointment, the (Steering Committee) election committee will reach out to
11+
the newly elected Steering Committee member and ask which committee they intend
12+
to continue with.
13+
14+
The committee where that individual vacated their seat will fill that vacancy
15+
per existing election or committee vacancy rules.

0 commit comments

Comments
 (0)