Page tree

Draft for voter and candidate criteria for Tungsten Fabric TSC.docx

Draft for voter and candidate criteria for Tungsten Fabric TSC

 

 

Community-at-Large

Members of this pool are expected to actively participate in the project governance, policy creation, budget, project evangelism, event planning and operation. This pool focuses broadens the TSC to include community members who are not technical code contributions, but nevertheless focused on project growth and adoption.

 

  * Seats: 5

  * Voters Qualifications:

-    Must be ATCs or ACCs

  * Candidates Qualifications:

-    Must be a valid Voter

-    No more than one candidate per company can be selected for this pool. In case two candidates from a single company are in top 5, candidate with most votes takes the seat. Candidate with lower votes is discarded and next ranked choice candidate is selected.

-    Must have a technical or marketing

  * Duplicate Voter Strategy: Vote-per-Person (?)

Technical Project Leadership

Members of this pool are expected to actively drive project technical strategy, including defining use cases, setting project technical direction including release schedule and content and driving development, QA, build and release activities for the project

 

* Seats: 5

* Voters Qualifications:

- Must be an ATC or TSC ATC

* Candidates Qualifications:

-    Must be a valid Voter

-    No more than one candidate per company can be selected for this pool. In case two candidates from a single company are in top 5, candidate with most votes takes the seat. Candidate with lower votes is discarded and next ranked choice candidate is selected.

-    Must hold a technical leadership position in their companies (Architect, Distinguished Engineer, CTO etc)              

  * Duplicate Voter Strategy: Vote-per-Person (?)

ARB representative

Members of this pool are expected to drive project detailed architecture and review specs and code to insure across the board compliance with the Tech and ARB decisions.

 

* Seats: 1

* Voters Qualifications: Current ARB member

* Candidates Qualifications: Current ARB member

* Duplicate Voter Strategy: Vote-per-Person (?)

 

 

Active Technical Contributors (ATCs)

 

1) Active contribution to TF project by contributing code/patches, which are approved by project PTL/core members. The contribution is not limited to code, it could be documentation or other contributions. For 2018 to broaden the voter base, ATC can be anybody with at least one approved/merged patch per 12 month. For 2019 and beyond ATC must contribute 5 approved/merged patches per 12 months or have active committer status for any of the project repos and provide 20 reviews per 12 month period.

 

2) TSC approved ATCs. TSC, at its sole discretion, may use one of the following criteria to qualify a candidate as ATC:

a. Active participation in the TSC calls (e.g. x% participation in TSC calls in past “n”  months – TSC reserves the right to change “x” and “n” at its discretion)

b. Candidate leading/driving/contributing to sub-teams or sub-projects related to TF

c. Candidate championing or aligning TF Technical charter among other projects within or outside LFN/LF

3) ATC designation will be maintained using a rolling 12 months window of contributions.

4) TSC reserves the right to modify/change these criteria based upon the circumstances from time to time

 

Active Community Contributors (ACCs)

 

1) Active contribution to TF policy creation, budget, evangelism, marketing, event activity and other non-technical project tracks.

2) Qualifications. Standing active participation in community meetings. Active is defined as execution of action items, participation in planning or execution of events and other outreach activities, contributions to community documents.

3) 1 Calendar year commitment is expected.