Kubernetes elects three members to its Steering Committee

Kubernetes' governance has to accommodate contributors whose employers also have commercial interests in the project. The 2018 Steering Committee election makes that tension explicit in its rules for endorsement and campaigning. The October 15 results announcement names Aaron Crickenberger, Davanum Srinivas and Tim St. Clair as the elected members, each beginning a two-year term. The announcement records 307 voters who cast ballots.

I care about this governance because depending on Kubernetes also means depending on the community which maintains its shared interfaces. Technical mechanisms can preserve compatibility only if people agree on responsibility for maintaining them. An elected body with a stated remit gives contributors somewhere to address the structure of that responsibility beyond a single technical disagreement.

The election fills a governance role

The 2018 voters guide describes three seats due for reelection. It distinguishes the technical direction shaped by Special Interest Groups and Working Groups from the Steering Committee's responsibility for project and community health. That division matters when interpreting an election result. Electing committee members does not replace the technical work performed in the project's subject-specific groups.

The guide gives concrete examples of the committee's remit. These include project values and scope, governance structures and policies for contributor roles. It also covers rules for creating community groups and the transparency and accountability of those groups. Such work determines how technical collaboration is organized, even when it does not settle a particular API design or implementation choice.

The September election announcement identifies SIG governance as a recurring committee topic during the year. It describes Kubernetes as a distributed community whose SIGs and Working Groups perform work within their areas. The election therefore renews part of the body responsible for how those units participate in the larger project.

This is useful context for users as well as contributors. A project can distribute implementation authority while still needing common rules about group recognition and contributor progression. Without that distinction, an operator might mistake every governance question for an argument about a feature. The voters guide instead identifies organizational decisions with their own process and elected representatives.

Endorsement crosses employer boundaries

The voters guide requires a nominee to obtain endorsements from three eligible voters representing three different employers. An eligible nominee can count toward that total. This requirement makes nomination more than a statement of interest by one person. It asks for support across employer boundaries before the candidacy proceeds.

Candidate statements are limited to 300 words and submitted as biographies in the election directory. That gives voters a comparable place to read the candidates' platforms and intentions. The process records those statements in the same public repository as the election guide. A voter can inspect the stated basis of a candidacy alongside the rules which govern participation.

The guide also explicitly discourages corporate campaigning. Candidates are asked to run as individuals on the basis of their community contributions, outside their corporate roles. Election officers and Steering Committee members pledge to recuse themselves from electioneering. Those restrictions acknowledge that affiliation exists while trying to prevent institutional position from determining how the election is conducted.

The results announcement lists the winners' affiliations as Google, Huawei and Heptio respectively. That information describes the elected individuals' employers at the time. It should not be interpreted as allocating company-owned committee seats. The voters guide's campaigning rule places the candidacy with the individual and the individual's contribution to the community.

Ranked voting supplies the selection procedure

The published process uses a time-limited Condorcet ranking through Cornell's CIVS service, with the Schulze method. Voters rank candidates and can express no opinion. The guide also calls for employer diversity constraints under the election charter and specifies a coin flip in the event of a tie. These are stated selection rules rather than criteria inferred after the winners are known. The guide identifies Paris Pittman, Ihor Dvoretskyi and Jorge Castro as the election officers, giving contributors named contacts responsible for the election process and its published instructions.

Voting opened in September and the guide scheduled its close for October 3, with a community-meeting announcement on October 4. The October 15 blog post supplies the written results used here. Keeping those dates distinct avoids treating the publication date of the results article as the beginning or entirety of the election process.

I regard the continuing access to committee work as relevant to the result. The announcement invites participation through backlog issues and pull requests, and points readers to recorded committee meetings. An election periodically selects representatives, while those channels allow contributors to examine and discuss the work between elections. The new members begin their terms within that existing process for public project governance.