This repository contains Kata Containers Elections reference documents and tooling to run elections.
The Kata Architecture Committee is comprised of seven seats, elected by the eligible community, and one Committee Chair, selected by the five Architecture Committee members.
The Architecture Committee elections take place every six months, as outlined in the Architecture Committee section of the Community README.
The election process begins three calendar weeks prior to the election.
- One week for candidates to submit their candidacy
- One week "debate period" for electorate to pose questions on the community mailing lists to learn the candidates platforms
- One week for voting
- Results announced
Contributors (defined as anyone who has had code merged in the Kata Containers project in the last 12 months prior to the first day of the nomination period) are eligible to vote in Architecture Committee elections.
Anyone who has made contributions to the Kata Containers project is eligible to run. Candidates submit their candidacy by adding a text file to the corresponding election folder under the community repo with their interest and platform, and announcing their candidacy on the community developer mailing list.
There are no term limits for Architecture Committee seats, but in order to encourage diversity, no more than two of the five seats may be filled by members with the same company affiliation. If a third member would be in violation of the diverse affiliation rule, the seat is awarded to the next highest scoring candidate who would not violate the rule. Members who change affiliation between elections in a way that violates the diverse affiliation rule are not required to relinquish their seat, however, the rule will be enforced and applied in the following election.
Architecture Committee members guide the technical direction of the Kata Containers project. This includes, but is not limited to:
- Serving the Kata technical community
- Driving technical direction
- Handling interactions with other governance bodies
- Acting as the final call in technical disputes
- Ensuring inclusive, open collaboration and development
- Identifying gaps in technical direction or community health
- Attending Architecture Committee meetings
- Regular participation (and advanced notice of absences) in online Arch Committee meetings and in-person meetings is expected
- Actively participates in Kata Containers design and development
- Not restricted to code contributions, but active input and guidance is expected
The Architecture Committee election uses CIVS with Condorcet method voting. You can find information about how to set up the voting on the related OpenStack wiki.
Due to CIVS policy, to vote in private CIVS polls, everyone in the electorate must opt in to email communication. CIVS has a dedicated page to register the email address they are using on GitHub. Once someone has opted into receiving e-mail from CIVS it should allow future ballots from any poll to be sent to the same e-mail address.
See the election tools documentation.
See the election process documentation for details on the process that election officials need to follow to successfully execute the AC election.
-
April 2024
-
October 2023
-
April 2023
-
November 2022
-
March 2022
-
September 2021
-
February 2021
-
September 2020
-
February 2020
-
September 2019
-
March 2019
-
September 2018 election