The Node.js Foundation Technical Steering Committee is the technical governing body of the Node.js Foundation. It admits and oversees all top-level Projects in the Node.js Foundation. It also elects a representative to the Node.js Foundation Board of Directors.
For more details read the TSC Charter adopted by the Node.js Foundation Board of Directors on June 17th 2015.
If your project is interested in joining the Node.js Foundation please read the Project Lifecycle.md documentation.
The TSC is responsible for Node.js Core project, a number of projects depended upon by Node.js Core and a number of projects adjacent to Node.js Core.
Node.js Core is defined as the code project existing in the repository located at https://github.com/nodejs/node minus the vendored projects included in the codebase, specifically those located in the deps and tools directories that are copied in from externally maintained repositories.
Also included in the Node.js Core project are projects required to plan, test, build, document and ship Node.js releases but are not significant enough to require independent management and administration. These projects are located in the following repositories:
- https://github.com/nodejs/docs
- https://github.com/nodejs/testing
- https://github.com/nodejs/node-eps
- https://github.com/nodejs/security (private)
Additional projects fall within the TSC's scope of responsibility which are dependents of Node.js Core in that they are required to plan, test, build, document and ship Node.js releases, yet are significant enough to require independent management and administration. These projects are located in the following repositories:
- https://github.com/nodejs/nodejs.org
- https://github.com/nodejs/http-parser
- https://github.com/nodejs/citgm
- https://github.com/nodejs/build
- https://github.com/nodejs/docker-node
- https://github.com/nodejs/benchmarking
- https://github.com/nodejs/readable-stream
- https://github.com/nodejs/secrets (private, administered by build)
- https://github.com/libuv/libuv (currently under Incubation)
The TSC is responsible for a number of projects that are not strictly required to plan, test, build, document and ship Node.js releases. Projects that are adjacent are either created from within the technical organization managed by the TSC or are adopted into that organization from outside. In the case of adopting existing projects, once the TSC has decided that adoption appropriate, it should seek agreement from the Node.js Foundation Board for such adoption as it impacts on the scope of technical activities of the Foundation.
Current adjacent projects that are within the TSC's scope of responsibility can be found at the following locations:
- https://github.com/nodejs/github-bot
- https://github.com/nodejs/installer
- https://github.com/nodejs/nan
- https://github.com/nodejs/nodereport
- https://github.com/nodejs/node-gyp
In being responsible for these projects and resources, the TSC exercises autonomy to set up management and administrative structures for the purpose of:
- Code and documentation creation and changes
- Standard definitions covering contributions of code, documentation and other materials
- Releases: types, schedules, frequency, delivery mechanisms
- Decisions regarding dependents of the Node.js Core project, including what those dependencies are and how they are bundled with source code and releases
- Creating new repositories and projects under the nodejs GitHub organization as required
- Setting overall technical direction for the Node.js Core project, including high-level goals and low-level specifics regarding features and functionality
TSC members are responsible for top level technical community concerns. The role is mostly administrative and is responsible for admitting new Top Level Projects, Top Level Working Groups, and advocating for any needs in the technical side of the foundation to the Node.js Foundation Board of Directors.
TSC members can nominate new members at any time. Candidates for membership tend to be people who have a competancy for community management and a high tolerance and patience for process minutiae as the TSC delegates most of its responsibilities to other projects and working groups.
Every Top Level Project not currently incubating can appoint someone to the TSC who they elect at their own discretion.
Avatar | Information |
---|---|
Rod Vagg @rvagg rod@vagg.org Committee Chair Board Director |
|
Ben Noordhuis @bnoordhuis info@bnoordhuis.nl |
|
Bert Belder @piscisaureus bertbelder@gmail.com |
|
Brian White @mscdex mscdex@mscdex.net |
|
Bryan Hughes @nebrius bryan@nebri.us |
|
Chris Dickinson @chrisdickinson christopher.s.dickinson@gmail.com |
|
Colin Ihrig @cjihrig cjihrig@gmail.com |
|
Fedor Indutny @indutny fedor.indutny@gmail.com |
|
James Snell @jasnell jasnell@gmail.com |
|
Jeremiah Senkpiel @fishrock123 fishrock123@rocketmail.com |
|
Shigeki Ohtsu @shigeki ohtsu@iij.ad.jp |
|
Trevor Norris @trevnorris trev.norris@gmail.com |
-
Mentors
Project mentorship is not a technical role. In fact, mentors are discouraged from giving technical advice to projects. Instead, the purpose of mentorship is to encourage and improve a projects ability to be participatory, transparent, and effective. Mentors are there to help projects adopt and iterate on policies and processes that achieve these goals and eventually allow them to graduate the incubation phase.
* Mikeal Rogers (@mikeal) Currently assigned to Express. * James Snell (@jasnell) Currently assigned to Express. * Rod Vagg (@rvagg) Currently assigned to libuv. * Alexis Campailla (@orangemocha) Currently assigned to libuv.
-
Top-Level Projects
-
Core TLP
-
Core WGs (streams, http, Intl)
The Node.js TSC is chartered to oversee the technical governance of all Top Level Projects and Working Groups under the Node.js Foundation. The TSC establishes the default governance, conduct, and licensing policies for all Top Level Projects. Top Level Projects and Working Groups have broad powers of self-governance.
To propose a change or addition to policies or processes that are intended to
cover all Top Level Projects and Working Groups in the foundation, a PR should
be opened in the nodejs/TSC
repository.
The pull request can be labeled tsc-agenda
to request that it be put on the
agenda for the next TSC meeting.
The Node.js Foundation Board of Directors retains certain rights (especially legal considerations). If the TSC endorses a proposal, they will escalate to the Node.js Foundation Board of Directors when required to do so.
In some cases, existing individual groups have the right to refuse changes to their charters. The TSC can not mandate existing working groups alter their charters. If such a situation arises, the TSC may decide to revoke the group's charter.