The self-nomination period for the 2021 TSC Election has begun.  If you are interested in self-nominating to serve the community as a member of the Technical Steering Committee, please do so here: https://wiki.tungsten.io/x/IwA2Ag

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.

The nomination period for Chairperson will begin immediately following the conclusion of the TSC Election.

• The self-nomination period will begin 18 Feb 2021
• The self-nomination period will end 04 Mar 2021.

The TSC is responsible for:

• Setting high level architecture goals and coordinating overall project architecture and technical direction
• Selecting technology stack, software features and supported hardware including
• Approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project’s scope);
• organizing sub-projects and removing sub-projects;
• Developing Project use cases;
• Defining and monitoring Project technical processes and interfaces with third party code and external projects including creating sub-committees or working groups to focus on cross-project technical issues and requirements;
• Overseeing the Infrastructure Working Group other TSC working groups;
• Appointing representatives to work with other open source or open standards communities;
• Establishing community norms, workflows, issuing releases, and security issue reporting policies;
• Approving and implementing policies and processes for contributing (to be published in the CONTRIBUTING file) and coordinating with other project committees to resolve matters or concerns that may arise as set forth in Section 7 of this Charter;
• Engaging in discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects;
• Setting target dates for software development and testing;
• Coordinating any marketing, events, or communications regarding the Project with the Manager of LF Projects and the Marketing Advisory Council of the LF Networking Fund of The Linux Foundation (“LFN”);
• Establishing a vetting process for maintaining security and integrity of new and/or changed code base and documentation, including vetting for malicious code and spyware; and
• Establishing a security issue reporting policy and resolution procedure.