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 OpaVote voting URLs are sent out.
In the event that there is any technical issue with either the lists.io email service or the OpaVote 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
The self-nomination period will end
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.
If you are interested in self-nominating for a seat on the Technical Steering Committee, please input the following information below:
Representative Group: Technical / Community
Short Biography: Here is a bit about myself and why you should vote for me.
Statement of Intent: What I plan to do to improve Tungsten Fabric
Technical Representative Nominations:
Name: Sayali Mane
Representative Group: Technical
Short Biography: I am a Senior Software Engineer working within Juniper's Data Center Business Unit to define and build cloud-native Software Defined Networking solutions. I have worked across various features for contrail, Tungsten Fabric as well as cloud-native architecture. As an active developer, I have contributed to open-source and Juniper's propriety solutions. I also act as reviewer on config module in SDN based solutions.
Statement of Intent: I have worked extensively in cloud-native technologies. As a techie-programmer, I believe I can contribute more to the community. I have been always keen on working closely with community even in my early career. I have experience working on another Linux Foundation Project from Hewlett-Packard. I hope to bring that experience and more to the table of Tungsten Fabric.
Community Representative Nominations:
Name: Nick Davey
Representative Group: Community
Short Biography: I am a Product Line Manager working within Juniper's Data Center Business Unit to define and build cloud-native Software Defined Networking solutions. I have worked with mobile operators, wireline providers, and cloud builders to take software defined networking and automation solutions from the lab into production. I am a quadruple JNCIE(CLOUD/SP/SEC/ENT), with over a decade of experience helping large enterprises, and service providers design and deploy differentiated service offerings.
Statement of Intent: I enthusiastically believe that SDN is the key to a successful large-scale cloud deployment. As a cloud technology enthusiast and experienced Tungsten Fabric user I have a deep respect for the role of Tungsten Fabric in providing connectivity to the world's largest OpenStack deployments. If elected I hope to use this position to educate our ecosystem partners and the broader cloud community about the necessity and amazing potential of Tungsten Fabric. I will work to engage closer with our engineering partners across the Tungsten Fabric community and bring broader engagement to our release model. Finally, I will focus in particular on an improved new user experience, through improved documentation and content generation.
Name: Ian Rae
Representative Group: Community
Short Biography: Put up my hand a few years ago at the original Tungsten Fabric meeting for the governance committee to help shepherd this project into the open source community. Background in evolutionary genetics, I grew up on the internet and I have spent 20+ years in the tech industry, with a focus on application networking - I was lucky to be exposed to open source software and cloud computing very early after their inception. In addition to running multiple small tech companies, I serve on multiple boards including Genome Canada and Air Transat.
Statement of Intent: Continue the worthy mission of unlocking and enabling a healthy open source community to take hold and scale around this impressively flexible hybrid cloud networking technology. What I now lack in terms of technical contribution skills I can hopefully make up for at the community and governance level. The goal is to get this project into orbit!