You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

If you would like to self-nominate for the TSC, please list your name, represented group, a short biography and statement of intent for running.

For details on eligibility and mechanics, please see this page.

The nomination period will end December 17th, 2018.

The TSC is responsible for: i) Setting high level architecture goals and coordinating overall project architecture and technical direction ii) Selecting technology stack, software features and supported hardware including iii) approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project’s scope); iv) organizing sub-projects and removing sub-projects; v) Developing Project use cases; vi) 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; vii)Overseeing the Infrastructure Working Group other TSC working groups; viii) Appointing representatives to work with other open source or open standards communities; ix) Establishing community norms, workflows, issuing releases, and security issue reporting policies; x) 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; xi) Engaging in discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; xii)Setting target dates for software development and testing; xiii) 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”); xiv) 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 xv) Establishing a security issue reporting policy and resolution procedure.


Template:

Name: <>

  • Small photo
  • Represented Group - <TC|CC>
  • Short Biography
  • Statement of Intent: <>

Nominations:

Name: Randy Bias

  • Represented Group - Everyone
  • Short Biography: I run open source strategy for Juniper and was the instigator inside of Juniper for the community "reboot".  I previously served on the OpenStack Board of Directors and currently serve on the Linux Foundation Networking (LFN) TAC as Juniper's representative.  As one of the visionaries for the community, I'm uniquely positioned to help Tungsten Fabric achieve it's full future potential.  And as most people know, I'm a no BS guy that is in earnest to help TF grow without Juniper Networks over the long term.
  • Statement of Intent: I am looking to more deeply engage with the community by becoming a voting member of the TSC.
  • No labels