TSC Membership Definitions
Active Community Members: Anyone from the TF community with twenty (20) or more measurable contributions during the previous 12-month period, inclusive of code merged, code reviews performed, wiki page edits, or JIRA activities.
Initial TSC Makeup
The initial TSC will be made up of one (1) member from each participating company as agreed by the founding members. One (1) alternative TSC member from each company may also be named. The TSC is made up as follows to date.
The TSC will elect from amongst voting TSC members a chairperson for a term of one year according to the XGVela Technical Charter. The TSC shall hold elections to elect a TSC Chair annually; there are no limits on the number of terms a TSC Chair may serve.
The TSC Chair is responsible for:
- Leading TSC meetings;
- This responsibility may be delegated to the TSC Co-Chair, or to another TSC member (in such case, this is to be informed via the TSC email list)
- Representing the technical community to external organizations.
- These responsibilities may be delegated to the TSC Co-Chair, or to another member of the technical community.
- Lead the TSC in the execution of the TSCs responsibilities (section 4.3).
TSC Decision Making Process
Decisions of the TSC should be made by majority vote of TSC Members.
TSC Chair/Co-Chair/Coordinator Elections
The TSC Chair/Co-Chair/Coordinators shall be elected separately. There is no prohibition against a person holding multiple roles.
TSC Chair Candidates
Candidates for TSC Chair must be TSC Members.
Candidates must self nominate.
Any community member (regardless of TSC membership) is eligible to serve as a coordinator. Nominees should have subject matter experience in the relevant coordination area.
Candidates must self nominate.
TSC Chair/Coordinator Voters
Only TSC Members are eligible to vote for TSC Chair/Co-Chair/Coordinator.
TSC Chair/Coordinator Election Mechanics
Election of a TSC Chair/Coordinator shall use a multiple-candidate method, e.g.:
Condorset; or Single Transferable Vote
TSC Member Elections
Candidate and Voter Eligibility
- Any Active Community Member (regardless of LFN membership), is eligible to run for a TSC seat.
- Any Active Community Member (regardless of LFN membership), is eligible to vote in a TSC election.
- Eligibility is effective as of the date and time the nomination process starts.
- The TSC will be made of of (1) member per participating company. This may be amended by vote as the project grows.
TSC Term Duration
- TSC term duration is 1 year starting in October of the calendar year. Elections will be held in October for the calendar year.
TSC Member Candidates
- There are no limitations on the number of candidates that can run for a TSC seat, nor is there a limit to the number of candidates from any company, or group of related companies that can run in a TSC election
- Candidates must self nominate
TSC Member Standing Down
- If a TSC member is no longer able to perform the TSC duties, the TSC member may inform via an email to the TSC email list.
- If a TSC member moves companies, that member must notify the TSC via an email to the TSC email list. That TSC member may remain a member unless: 1) the moves places the member in conflict with the TSC composition rules, or 2) the TSC member (at his/her determination) will no longer be able to perform their TSC duties.
Replacement of a TSC member standing down
- In the event of a TSC member standing down:
- If the TSC position is from one of the elected positions (i.e. non reserved seat), an election for that single position is held within 60 days of notification. The conditions of the election are the same as for any TSC election.
- If the said position was of that of a TSC chair, then the TSC chair position will undergo re-election after the successful appointment or election of the new TSC member.
- When the next General TSC election is held, any seat filled by a Replacement of a TSC Member (per above) will also be included in the general TSC election.
Responsibilities of the TSC.
Subject to the Technical Charter, the TSC is responsible for:
- Defining XGVela release vehicles (such as a Coordinated Release) that align with the Project’s mission,
- Fostering cross-project collaboration,
- Serving as XGVelas’s primary technical liaison body with other consortiums and groups,
- Developing an architecture,
- Setting simultaneous release dates,
- Defining release quality standards,
- Defining technical best practices and community norms (including the establishment and maintenance of a Development Process),
- Monitoring technical progress,
- Mediating technical conflicts between Committers and PTLs,
- Organizing inter-project collaboration,
- Coordinating technical community engagement with the end-user community.
The TSC, at its discretion, may establish subcommittees to assist the TSC with its responsibilities and provide expert guidance in technical subject areas (e.g., architecture or security).
Subcommittee Membership Eligibility
Each subcommittee shall determine its own membership eligibility, in consultation with the TSC. It is expected that subcommittee membership shall be open to all XGVela Contributors; however, subcommittees may impose restrictions such as the number of participants from a single company. While the desire may be to keep its size and scope limited, each subcommittee shall be open to the TF membership. Also, all elected TSC members are eligible to join a subcommittee
Subcommittee Chair / Vice Chair
Each subcommittee may elect a Chair and optionally a Vice-Chair who is responsible for leading meetings and representing the subcommittee to the TSC.
Subcommittee Chair / Vice Chair Elections
The Chair or Vice-Chair will be elected by members of the subcommittee as of the date the nomination process starts for the election.
Subcommittee Voter Eligibility
Voting for a Chair or Vice-Chair is not limited to XGVela member companies. However only 1 Subcommittee member from each company, or group of related companies may vote in the election.
For the purpose of this document, “Related Company” shall mean any entity (Company-A) which controls or is controlled by another entity (Company-B) or which, together, is under the common control of a third party (Company-C), in each case where such control results from ownership, either directly or indirectly, of more than fifty percent of the voting securities or membership interests of the entity in question; and “Related Companies” are entities that are each a Related Company as described above.
Subcommittee Election Confirmation
The elected Chair (and/or Vice-Chair) is submitted to the TSC for confirmation. The TSC decides to accept the outcome or requests a new voting.
Subcommittees are advisory in nature, and not authoritative. They provide advice to projects and to the TSC.
Subcommittees operate on a rough consensus basis. If the subcommittee is unable to reach consensus on what advice to offer, the subcommittee Chair shall raise the issue with the TSC, where a formal vote can be taken, or advise the project that the subcommittee cannot reach consensus.
TSC subcommittee lifecycle.
Creation of a TSC subcommittee
The TSC decides the creation of a subcommittee in accordance with TSC decision procedure.
In order to create a TSC subcommittee, a TSC member shall make a proposal to the TSC (via TSC email list) that that shall cover at least the following:
- TSC subcommittee name.
- TSC subcommittee purpose:
- TSC subcommittee expected deliverables:
- TSC subcommittee starting participants:
- Optionally TSC subcommittee definition of done:
Update of a TSC subcommittee
The TSC can modify a TSC subcommittee via a TSC decision. To request such a modification, a request is made to the TSC email list.
Conclusion of a TSC subcommittee
The TSC decides the termination of the TSC subcommittee in accordance with the TSC decision procedure. The submission of a request to terminate the TSC subcommittee should cover:
- TSC subcommittee name
- TSC subcommittee deliveries
- Motivation for termination of TSC subcommittee