Skip to content
The Node.js Technical Steering Committee
Branch: master
Clone or download

Latest commit

mhdawson doc: add minutes for meeting 18 March 2020 (#839)
* doc: add minutes for meeting 18 March 2020

PR-URL: #839
Reviewed-By: Ruben Bridgewater <>
Reviewed-By: Beth Griggs <>
Reviewed-By: Daniel Bevenius <>
Reviewed-By: Colin Ihrig <>
Reviewed-By: Matteo Collina <>
Latest commit a0f357d Mar 25, 2020


Type Name Latest commit message Commit time
Failed to load latest commit information.
Applications Add TLP application for express Feb 10, 2016
BasePolicies update boilerplate to remove WG size specifics (#579) Aug 8, 2018
Streaming doc: describe workaround for authorization error (#826) Feb 24, 2020
meetings doc: add minutes for meeting 18 March 2020 (#839) Mar 25, 2020 doc: move Code of Conduct to admin repo Nov 23, 2017 travel-fund: move to nodejs/admin (#460) Jan 6, 2018 doc: move Moderation Policy to Admin Repo Nov 23, 2017 doc: on/offboarding from HackerOne (#798) Jan 9, 2020 doc: describe OpenSSL maintenance strategy Apr 4, 2019 update DCO to 1.1 Apr 29, 2016 chore: remove mention of the defunct Evangelism WG (#819) Feb 18, 2020 doc: describe security workflow (#799) Jan 22, 2020 doc: update strategic initiatives (#833) Mar 25, 2020 doc: update TSC charter (#698) Jul 10, 2019 decharter website working group (#761) Oct 8, 2019

The Node.js Technical Steering Committee

The Node.js Technical Steering Committee (TSC) is the technical governing body of Node.js. It is described in the TSC Charter.

TSC Scope

The TSC is responsible for the Node.js Core project, a number of projects depended upon by Node.js Core, and a number of projects adjacent to Node.js Core.

The TSC exercises autonomy in managing its responsibilities and seeks agreement from the OpenJS Foundation Board on any change to the scope of those responsibilities as defined below.

Node.js Core

Node.js Core is defined as the contents of the repository located at from which the node executable and associated packages are built, excluding the vendored projects included in the codebase located in the deps and tools directories that are copied in from externally maintained repositories.

Dependent Projects

Additional projects fall within the TSC's scope of responsibility which are dependencies of Node.js Core in that they are required to plan, test, build, document and ship Node.js releases.

These projects are located in the following repositories:

Adjacent Projects

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 OpenJS Foundation Board for such adoption as it impacts on the scope of technical activities of the Foundation.

If the OpenJS Foundation Board wishes to adopt an existing project, it must seek agreement from the TSC that such adoption is appropriate and that any changes to scope that it entails are acceptable.

Current adjacent projects that are within the TSC's scope of responsibility include:

List of TSC Responsibilities

The TSC exercises autonomy in setting up and maintaining procedures, policies, and management and administrative structures as it deems appropriate for the maintenance and operation of these projects and resources.

Included in the responsibilities of the TSC are:

  • Managing code and documentation creation and changes for the listed projects and resources
  • Setting and maintaining standards covering contributions of code, documentation and other materials
  • Managing code and binary releases: types, schedules, frequency, delivery mechanisms
  • Making decisions regarding dependencies 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
  • Setting and maintaining appropriate standards for community discourse via the various mediums under TSC control
  • Setting and maintaining governance rules for the conduct and make-up of the TSC, Working Groups and other bodies within the TSC's domain

Many of these responsibilities will be delegated by the TSC to appropriate bodies such as the Working Groups.

TSC Members

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 project to the OpenJS 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.

A current list of TSC members is maintained in the main Node.js repository.


Many teams/groups post meeting videos to the Node.js YouTube channel.

Any GitHub team maintainer is allowed Manager access to the Google Plus account allowing them to add/manage video content and schedule events (live broadcasts).

Members of the TSC are allowed Owner access to the Google Plus account. This role can do all Manager activities and add/remove other members from the Google Plus account.

To request access, open an issue.

Strategic Initiatives

At any one time the Node.js project has a number of strategic initiatives underway. The goal of the TSC is to have a champion for each of these initiatives and to support the initiatives in order to enable their success.

For more information look here: Strategic Initiatives

Top-Level WGs and TLPs

  • Working Groups
  • Top-Level Projects
  • Core TLP
  • Core WGs (for example, streams)

Policy Change Proposal Process

The Node.js TSC is chartered to oversee the technical governance of all Top Level Projects and Working Groups under Node.js. 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 OpenJS Foundation Board of Directors retains certain rights (especially legal considerations). If the TSC endorses a proposal, they will escalate to the OpenJS 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.

You can’t perform that action at this time.