TSC Voting Members
Committer RepresentativesCommunity Representatives

 Sayali Mane - Juniper


Nick Davey - Juniper


Chandra Mohan - Juniper


Ian Rae - CloudOps

Community Elected Roles
Release Manager

Technical Representatives consist of Committers with 5 or more measurable commits within the last 12 months. This will be determined by the union of a Gerrit query and a GitHub query. The Gerrit query will be run against https://gerrit.tungsten.io. 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. 

Active Community Contributors.  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.

The TSC is responsible for:

  1. Setting high level architecture goals and coordinating overall project architecture and technical direction

  2. Selecting technology stack, software features and supported hardware including

  3. Approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project’s scope);

  4. Organizing sub-projects and removing sub-projects;

  5. Developing Project use cases;

  6. 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;

  7. Overseeing the Infrastructure Working Group other TSC working groups;

  8. Appointing representatives to work with other open source or open standards communities;

  9. Establishing community norms, workflows, issuing releases, and security issue reporting policies;

  10. 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;

  11. Engaging in discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects;

  12. Setting target dates for software development and testing;

  13. 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”);

  14. 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

  15. Establishing a security issue reporting policy and resolution procedure.