Skip to content

Commit 75c1333

Browse files
committed
CHARTER: s6: rework TOB description and procedures
The description of the TOB had several pretty large omissions such as the election procedure (only the initial TOB election is described, and it doesn't match the procedure in use today) as well as a lack of clarity around which group of maintainers need to vote to raise an issue with the TOB. This change does introduce new requirements for the TOB and the Executive Director, but the purpose of this change is to simply bring it in line with the existing procedure employed by the TOB. Signed-off-by: Aleksa Sarai <[email protected]>
1 parent 675f207 commit 75c1333

File tree

1 file changed

+104
-65
lines changed

1 file changed

+104
-65
lines changed

CHARTER.md

Lines changed: 104 additions & 65 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@
88
| 1.2+DRAFT | | | &bull; *(Section 2)* Simplify OCI Project definition and clarify scope. |
99
| 1.2+DRAFT | | | &bull; *(Section 5)* Simplify TDC description and enshrine all maintainers of OCI Projects as TDC Maintainers. |
1010
| 1.2+DRAFT | | | &bull; *(Section 6)* Unify TOB voting rules to always require a qualified super-majority for decisions. |
11+
| 1.2+DRAFT | | | &bull; *(Section 6)* Update TOB procedures, codify election process, and remove outdated sections. |
1112
| 1.2+DRAFT | | | &bull; *(Section 12)* Formalise changelog and version numbers. |
1213

1314
> **NOTE**: The "notice date" is the date at which OCI Members were given
@@ -316,12 +317,11 @@ g. The TDC will only accept influence through contribution. The primary means
316317

317318
## 6. Technical Oversight Board (TOB)
318319

319-
a. The TOB is responsible for managing conflicts, violations of procedures or
320-
guidelines and any cross-project or high-level issues that cannot be
321-
resolved in the TDC for OCI Projects. The TOB shall also be responsible for
322-
adding, removing or reorganizing OCI Projects. The TOB shall not dictate or
323-
interfere with the day-to-day work of individual OCI Projects or their
324-
decisions.
320+
a. The OCI shall have a Technical Oversight Board ("TOB"), which is responsible
321+
for managing conflicts, violations of procedures or guidelines and any
322+
cross-project or high-level issues that cannot be resolved by the TDC. The
323+
TOB shall not dictate or interfere with the day-to-day work of individual
324+
OCI Projects or their decisions.
325325

326326
b. The TOB shall be responsible for adopting any policies related to the scope
327327
of the TOB and ensuring they are documented publicly.
@@ -337,79 +337,118 @@ c. The TOB shall operate transparently with any discussions and mailing lists
337337
shall also require a representative from The Linux Foundation to ensure this
338338
option is not being abused.
339339

340-
d. While the initial TDC shall have one TDC, as the OCI evolves, the TOB may
341-
decide to establish a TDC per OCI Project, requiring contributors to earn
342-
maintainer status independently within each OCI Project in which they wish
343-
to participate.
344-
345-
e. The TOB shall be composed of nine (9) individuals elected for their
346-
expertise, contribution to the advancement of container technologies and are
347-
considered to be thought leaders in the OCI ecosystem. Anyone may be elected
348-
to the TOB, regardless of whether the individual is an employee of an OCI
349-
Member, so long as they are an OCI TDC participant. A TOB member is elected
350-
as an individual and not as a representative of his or her employer. No more
351-
than two (2) TOB members may be employed by the same entity or its
352-
affiliates. Affiliates shall be defined as entities owning 50% or more of an
353-
entity, or owned by or under common ownership with each other. TOB members
354-
may not designate alternative representatives.
355-
356-
f. TOB members shall be split into two (2) groups, serving for a term of two
357-
(2) years on a staggered basis, where one group is elected each year. The
358-
initial TOB will have four (4) TOB members who will only serve for a term of
359-
one year and five (5) TOB members that serve for a term of two (2) years.
360-
361-
g. The initial TOB shall be established through a nomination and election
362-
process. The first group from which four (4) TOB members shall be elected,
363-
will be nominated and elected by the current TDC maintainers, initially
364-
identified in Section 4(e), and serve for a period of one (1) year. Each TDC
365-
maintainer may nominate up to two (2) candidates for election, except that
366-
only one (1) nominee may be employed by the TDC maintainer’s own company.
367-
The second group from which five (5) TOB members shall be elected, will be
368-
nominated and elected by the OCI Members and serve for a period of two (2)
369-
years. Each OCI Member may nominate one (1) candidate for election.
370-
371-
h. Elections of TOB members shall be run using the Condorcet-IRV method
372-
through the Cornell online service (http://civs.cs.cornell.edu/).
373-
374-
i. The TOB shall elect a TOB Chair. The nominee with the most votes from the
375-
TOB members shall win the Chair position for a term of one (1) year. In the
376-
event of a tie vote, a random selection process (e.g. coin toss) shall be
377-
used to determine the winner. The TOB Chair shall have the responsibility to
378-
call meetings of the TOB and set TOB meeting agendas with input from TOB
379-
members.
380-
381-
j. The TOB shall meet on an as-needed basis, in a timely manner after issues
382-
are directed to the TOB from:
383-
384-
- i. the TDC by a simple majority vote of the maintainers when there is an
385-
issue that needs the resolution to assist the TDC to move forward,
386-
- ii. the TOB via a decision made using the process outlined in Section 6
340+
d. The TOB shall be composed of nine (9) individuals elected by the
341+
Maintainership Coalition for their expertise, contribution to the
342+
advancement of container technologies and are considered to be thought
343+
leaders in the OCI ecosystem. A TOB member is elected as an individual and
344+
not as a representative of his or her employer. TOB members may not
345+
designate alternative representatives.
346+
347+
e. An individual is incapable of being a member of the TOB if they at any point
348+
during their tenure they:
349+
350+
- i. are not a member of the TDC; or
351+
- ii. become unable to exercise their duties as a TOB member; or
352+
- iii. are employed by the same entity or affiliate as two (2) or more other
353+
TOB members. Affiliates shall be defined as entities owning 50% or more of
354+
an entity, or owned by or under common ownership with each other.
355+
356+
f. TOB members shall be split into two (2) groups counting four (4) and five
357+
(5) members each, both serving for a term of two (2) years on a staggered
358+
basis, with an election being held each year alternating between which
359+
group's seats are up for election.
360+
361+
g. The TOB membership shall be chosen through a nomination and election
362+
process, organised by the Executive Director. The procedure for nomination
363+
and election of seats shall be:
364+
365+
1. The Executive Director shall publicly call for nominations no less than
366+
four (4) weeks before the expiry of the current group of TOB seats, or
367+
immediately if the seats have already become vacant. The nomination
368+
period shall last a minimum of two (2) weeks.
369+
2. Each member of the Maintainership Coalition may privately nominate up to
370+
two (2) candidates, with no more than (1) nominated candidate being
371+
employed by the same entity or affiliate as the Maintainer. Affiliate
372+
shall be defined as in Section 6 (e)(iii) of this Charter. Information
373+
about which member nominated which candidate must remain private.
374+
3. The Executive Director shall call for a vote for the TOB seats with all
375+
nominated candidates (who are elligible under Section 6 (e) of this
376+
Charter) being included as choices on the ballot, using the voting
377+
procedure prescribed in Section 6 (j) of this Charter. Each member of the
378+
Maintainership Coalition is entitled to only one (1) vote, regardless of
379+
whether the individual is a Maintainer of a single or multiple OCI
380+
Projects. The voting period shall last a minimum of two (2) weeks.
381+
4. Upon the conclusion of the election, the members-elect shall become TOB
382+
members upon expiry (or vacancy) of the TOB seats.
383+
384+
h. Notwithstanding Section 6 (f) through (g) of this Charter, the initial TOB
385+
shall have its four (4) member group only serve a term of one (1) year and
386+
will be nominated and elected by OCI Members, with each OCI Member being
387+
permitted to nominate one (1) candidate for election and being given one (1)
388+
vote. For the avoidance of doubt, this procedure only applies to the initial
389+
TOB, and the five (5) member group of the initial TOB shall serve a term of
390+
two (2) years and be nominated and elected through the procedure defined in
391+
Section 6 (g) of this Charter.
392+
393+
i. After each election the TOB shall, before the dispatch of any other
394+
business, elect one (1) TOB member (using the procedure described in
395+
Section 6 (g) of this Charter) to be the TOB Chair, who shall hold that
396+
position for a term of one (1) year. In the event of a tie vote, a random
397+
selection process (such as a fair coin toss) shall be used to determine the
398+
winner. The TOB Chair shall have the responsibility to call meetings of the
399+
TOB and set TOB meeting agendas with input from TOB members.
400+
401+
j. Elections of TOB members and the TOB chair shall be run by the Executive
402+
Director, using the Condorcet-IRV method through the [Condorcet Internet
403+
Voting Service](https://civs.cs.cornell.edu/). Upon the completion of any
404+
vote using this procedure, the Executive Director must announce the results
405+
of the vote publicly.
406+
407+
k. The TOB shall meet on an as-needed basis to discuss any agenda set by the
408+
TOB Chair, who may set such an agenda at any time if they determine a
409+
meeting is necessary. Members of the TDC outside of the TOB may attend and
410+
participate in TOB meetings, but cannot vote on motions nor raise issues
411+
which are not part of the meeting agenda.
412+
413+
l. In the case of any issues being directed to the TOB, the TOB Chair must call
414+
a meeting in a timely manner with an agenda including the issues directed to
415+
the TOB, so that the TOB may resolve them. An issue may be directed to the
416+
TOB from:
417+
418+
- i. the Maintainers of one (1) or more OCI Projects, by a qualified
419+
majority vote of the set of Maintainers of the given OCI Projects, for an
420+
issue involving only the given OCI Projects; or
421+
- ii. the Maintainership Coalition, by a qualified majority vote; or
422+
- iii. the TOB via a decision made using the process outlined in Section 6
387423
(n) of this Charter; or
388-
- iii. the TOB Chair if they determine a meeting is necessary.
424+
- iv. the TOB Chair if they determine a meeting is necessary.
389425

390-
k. TOB meetings may be held in-person or via telephone or electronic
391-
conferencing.
392-
393-
l. Issues should be referred to the TOB sufficiently in advance of a meeting to
426+
m. Issues should be referred to the TOB sufficiently in advance of a meeting to
394427
provide an appropriate time for TOB members to evaluate the issues, and the
395428
positions of the TDC, the positions of users, as well as sufficient time to
396429
explore compromise solutions. It is expected an appropriate review should
397-
require at least a two-week review period, though it is recognized some
398-
timecritical circumstances may call for a shorter review (e.g. security
430+
require at least a two (2) week review period, though it is recognized some
431+
time-critical circumstances may call for a shorter review (such as security
399432
issues).
400433

401-
m. Quorum for holding meetings shall be established when two-thirds of TOB
402-
members are present.
434+
n. TOB meetings may be held in-person or via telephone or electronic
435+
conferencing. Quorum for holding meetings shall be established when
436+
two-thirds of TOB members are present. If the TOB is unable to form a
437+
quorum, the TOB Chair must call subsequent meetings in a timely manner with
438+
the same agenda until a quorum is formed.
403439

404-
n. The intention is for the TOB to operate by consensus. However, if consensus
440+
o. The intention is for the TOB to operate by consensus. However, if consensus
405441
cannot be achieved, the TOB shall vote on a decision. All TOB votes, either
406442
at TOB meetings, via email or electronic voting service, shall pass with a
407443
qualified super-majority (a two-thirds vote of the entire TOB membership in
408444
favour of the motion in question), on a one (1) vote per TOB member basis.
409445
For the avoidance of doubt, an abstain vote (or not voting) equals a vote
410-
against the motion in question.
446+
against the motion in question. If a vote is conducted outside of a TOB
447+
meeting, the vote will be organised by the Executive Director and must have
448+
a clearly established deadline at which point the votes will be tallied and
449+
announced by the Executive Director.
411450

412-
o. Any issues that cannot be resolved by the TOB shall be referred to The Linux
451+
p. Any issues that cannot be resolved by the TOB shall be referred to the Linux
413452
Foundation Executive Director for mediation, and, if necessary, for
414453
resolution by The Linux Foundation Board of Directors.
415454

0 commit comments

Comments
 (0)