Page tree
Skip to end of metadata
Go to start of metadata

Precedence

This page documents the details of how the election of Tungsten Fabric Technical Steering Committee members will take place. The Charter and Governance Document referenced on the Governance page take precedence over everything on this page. The mechanics described here are intended to provide the implementation details of the goals and structure laid out in those documents.  Section 5.1.1 of the Governance document states that the specifics of the election process will be documented by the “startup” TSC no later than December, 2018.  This page addresses that requirement. For a more detailed explanation of what the TSC is and how it is structured, please refer to the Charter and Governance document.

Acronym Definitions (derived from the governance document)

  • TSC = Technical Steering Committee = The union of the TC, the CC and one member elected by and from the ARB
  • TC = Technical Committee = Five people elected by and from the union of the ATC and TSC-ATC members
  • CC = Community Committee = Five people elected by and from the union of the ATC, TSC-ATC and ACC members
  • ARB = Architecture Review Board = Seven people elected by the union of project committers, PTLs and TSC members from the union of "Project Core" (which might not be clearly defined in the document, but I would read as synonymous with "committer") and TSC nominees. Furthermore, the document does spell out ARB qualifications and responsibilities more stringent than TC or CC qualifications and responsibilities. And for the initial startup period we agreed that five of the seven ARB members would be Juniper designated because we need time for non-Juniper people to demonstrate project architecture leadership and qualification.
  • ATC = Active Technical Contributor = At least one approved/merged patch in one release is required in the preceding 12 months prior to the election.
  • TSC-ATC = ATC by TSC vote rather than by commit history. Quoted straight out of the document "Any TSC member can nominate a community member for TSC-ATC status, providing evidence as to the good work done by the individual for the community. The TSC will then vote to approve or decline the individual’s TSC-ATC status. Such a designation is good for one year, and must be renewed by the TSC annually to remain current."
  • ACC = Active Community Contributor = Contributor approved by the TSC as having done non-technical work. Quoted straight out of the document "Any TSC member can nominate a community member for ACC status, providing evidence as to the good work done by the individual for the community. The TSC will then vote to approve or decline the individual’s ACC status. Such a designation is good for one year, and must be renewed by the TSC annually to remain current."

Location of Lists of Each Group and Category Defined Above

Candidate and Voter Eligibility Lists for TSC Election Process

There are three lists of eligible voters.  Generally a given individual would only appear in one list.  More information on the definition of each type is in the Governance document, but broadly speaking an ATC is technical and provides patches, a TSC-ATC is technical but has not provided patches, and an ACC provides important non-technical contributions. In general it is not necessary for a single person to have more than one status, but it is possible (e.g. a TSC-ATC makes their first commit and thus gains ATC status). Regardless of this, each person is only entitled to vote once per election (an ATC or TSC-ATC may vote in both the TC and CC elections.)

ATC

An Active Technical Contributor (ATC) is defined as having "At least one approved/merged patch in one release is required in the preceding 12 months prior to the election." This will be determined by the union of a Gerrit query and a GitHub query. The Gerrit query will be run against both https://review.opencontrail.org and https://gerrit.tungsten.io until the former has been retired for a full 12 months. Since a Gerrit change may consist of multiple patch sets, but only the final patch set that is merged enters into the repository there may be an ambiguity as to who the contributor is. For the purposes of ATC status, the author of the final patch set will be considered to be the contributor of the merged change. The TSC will have the right to inspect the script/query which is used by the Linux Foundation to pull the list of ATCs.

TSC-ATC

The list of TSC approved ATCs will be maintained in the docs repository at the following location: https://github.com/tungstenfabric/docs/tree/master/Governance/TSC-ATC_Members

ACC

The list of Active Community Contributors (ACCs) will be maintained in the docs repository at the following location: https://github.com/tungstenfabric/docs/tree/master/Governance/ACC_Members

Nomination

All candidates must self-nominate. In order to self-nominate, a person must be eligible. The governance document does not appear to prohibit a person from self-nominating for both the CC and TC, however the charter clearly states (section 3a) "the voting members of the TSC will vote on a one vote per voting member basis" so there is no value in a single person winning both elections. The TSC may wish to explicitly forbid nominating oneself for both elections.

Community Committee

  • Voter Criteria (i.e. eligible to vote in the election)
    • ATC, TSC-ATC or ACC
  • Candidate Criteria (i.e. eligible to self-nominate)
    • ATC, TSC-ATC or ACC
  • Community Committee Representation
    • 5 TSC Seats
    • Each seat determined by ranked voting of all candidates with the top 5 candidates from different, and unrelated companies winning the election.

Technical Committee

  • Voter Criteria (i.e. eligible to vote in the election)
    • ATC or TSC-ATC
  • Candidate Criteria (i.e. eligible to self-nominate)
    • ATC or TSC-ATC
  • Technical Project Leadership Representation
    • 5 TSC Seats
    • Each seat determined by ranked voting of all candidates with the top 5 candidates from different, and unrelated companies winning the election.

Architecture Review Board

The seven members of the ARB listed here https://github.com/tungstenfabric/docs/blob/master/Governance/ArchitectureReviewBoard/ARB_Members may select any one of their number to act as the ARB member of the TSC with the exception that any individual who is a member of either the CC or TC while also being a member of the ARB is not eligible since they are already a member of the TSC.

Voting Tools

Nominations will be solicited via an email from the Linux Foundation election coordinator to the DiscussDev and TSC mailing lists.

Elections will be performed using the Condorcet Internet Voting Service and managed by an election coordinator from the Linux Foundation. The election coordinator will use the eligibility lists above to create a private (by CIVS definition) poll. See the CIVS site for more details, but the main significant point is that CIVS will email each voter a unique URL. Consequently, it is essential that each eligible voter be able to receive email at the address with which they have been recognized as an ATC, TSC-ATC or ACC in order to vote in the election.

The result of the CIVS election will be an ordered list of candidates. For each election separately (TC and CC) the election coordinator will go down the list from highest to lowest rank and note the organization represented by each candidate. Per the governance document, there is no limit on the number of candidates from a single company who may be nominated, but there is a limit of one candidate per company who may be elected to each of the committees. Therefore, the election coordinator will skip over the 2nd, 3rd, etc candidate from any given company.

Example

In the example below, the numbers represent the CIVS rank of each candidate and the letters represent each candidate's company/organizational affiliation. The numbers in each column reflect only the CIVS rank in that specific election, i.e. rank 1 in the CC election and rank 1 in the TC election do NOT indicate the same person. The letters in each column DO represent the same company.


CCTC
Raw CIVS Rank
1 A2 B3 A4 C5 C6 D7 E
1 C2 D3 A4 F5 A6 G7 H8 I
Election Winners
1 A2 B4 C6 D7 E
1 C2 D3 A4 F6 G
Affiliation Summary

Company A: One CC and one TC rep

Company B: One CC rep

Company C: One CC and one TC rep

Company D: One CC and one TC rep

Company E: One CC rep

Company F: One TC rep

Company G: One TC rep

Company H: No representative

Company I: No representative

Election Timeline

The nomination period will be two weeks from the time that the nomination solicitation email is sent to both the Announce and Dev lists.

The election period will be two weeks from the time that the CIVS voting URLs are sent out.

In the event that there is any technical issue with either the lists.io email service or the CIVS service, the election coordinator may extend either period by up to one week without TSC approval. Any further extension will require TSC approval.

Election History and Effective Dates

2018

  • Nomination Period: (Tentative/Proposed) 01 December 2018 - 14 December 2018 (Tentative/Proposed)
  • Election Period: (Tentative/Proposed) 15 December 2018 - 30 December 2018 (Tentative/Proposed)
  • Effective Term of TSC: 01 January 2019 - 31 December 2019

2019

  • Nomination Period: (Tentative/Proposed) 01 December 2019 - 14 December 2019 (Tentative/Proposed)
  • Election Period: (Tentative/Proposed) 15 December 2019 - 30 December 2019 (Tentative/Proposed)
  • Effective Term of TSC: 01 January 2020 - 31 December 2020


  • No labels