{"id":15010623,"url":"https://github.com/nodejs/tsc","last_synced_at":"2025-05-15T03:04:40.087Z","repository":{"id":35925617,"uuid":"40213527","full_name":"nodejs/TSC","owner":"nodejs","description":"The Node.js Technical Steering Committee","archived":false,"fork":false,"pushed_at":"2025-04-09T20:51:27.000Z","size":3587,"stargazers_count":621,"open_issues_count":25,"forks_count":136,"subscribers_count":93,"default_branch":"main","last_synced_at":"2025-04-14T01:55:17.299Z","etag":null,"topics":["node","nodejs"],"latest_commit_sha":null,"homepage":"","language":"JavaScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/nodejs.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":"Security-Team.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2015-08-04T23:12:41.000Z","updated_at":"2025-04-11T02:35:01.000Z","dependencies_parsed_at":"2023-09-26T10:14:38.319Z","dependency_job_id":"551d4721-a55b-4623-9f59-aea1e8cf9450","html_url":"https://github.com/nodejs/TSC","commit_stats":{"total_commits":638,"total_committers":83,"mean_commits":7.686746987951807,"dds":0.8119122257053292,"last_synced_commit":"3f3606df0f44ac07a582128f068b3d699866a00d"},"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nodejs%2FTSC","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nodejs%2FTSC/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nodejs%2FTSC/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nodejs%2FTSC/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/nodejs","download_url":"https://codeload.github.com/nodejs/TSC/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248809032,"owners_count":21164895,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["node","nodejs"],"created_at":"2024-09-24T19:35:06.317Z","updated_at":"2025-04-14T01:55:24.145Z","avatar_url":"https://github.com/nodejs.png","language":"JavaScript","readme":"# Node.js Technical Steering Committee\n\nThe Node.js Technical Steering Committee (TSC) is the technical\ngoverning body of Node.js. It is described in the [TSC Charter][].\n\n## TSC scope\n\nThe TSC is responsible for the Node.js Core project, some projects\ndepended upon by Node.js Core, and several projects adjacent to Node.js\nCore.\n\nThe TSC exercises autonomy in managing its responsibilities and seeks agreement\nfrom the OpenJS Foundation Board on any change to the scope of those\nresponsibilities as defined below.\n\n### Node.js Core\n\n_Node.js Core_ is defined as the contents of the repository located at\n\u003chttps://github.com/nodejs/node\u003e from which the `node` executable and associated\npackages are built, excluding the vendored projects included in the codebase\nlocated in the [deps][] and [tools][] directories that are copied in from\nexternally maintained repositories.\n\n### Dependent projects\n\nAdditional projects fall within the TSC's scope of responsibility which are\ndependencies of Node.js Core in that they are **required** to plan, test, build,\ndocument, and ship Node.js releases.\n\nThese projects are located in the following repositories:\n\n* \u003chttps://github.com/nodejs/TSC\u003e\n* \u003chttps://github.com/nodejs/build\u003e — administration delegated to the Build Working Group\n* \u003chttps://github.com/nodejs/citgm\u003e — administration delegated to the Release Working Group\n* \u003chttps://github.com/nodejs/docker-node\u003e — administration delegated to the Docker Working Group\n* \u003chttps://github.com/nodejs/http-parser\u003e — administration delegated to the Core Technical Committee\n* \u003chttps://github.com/nodejs/node-eps\u003e — administration delegated to the Core Technical Committee\n* \u003chttps://github.com/nodejs/nodejs-dist-indexer\u003e — administration delegated to the Build Working Group\n* \u003chttps://github.com/nodejs/nodejs-latest-linker\u003e — administration delegated to the Build Working Group\n* \u003chttps://github.com/nodejs/nodejs-nightly-builder\u003e — administration delegated to the Build Working Group\n* \u003chttps://github.com/nodejs/nodejs.org\u003e — administration delegated to the Website Working Group\n* \u003chttps://github.com/nodejs/secrets\u003e — _private_, administration delegated to the Build Working Group\n* \u003chttps://github.com/nodejs/Release\u003e — administration delegated to the Release Working Group\n\n### Adjacent projects\n\nThe TSC is responsible for several projects that are not strictly required\nto plan, test, build, document, and ship Node.js releases. Adjacent projects are\neither created from within the technical organization managed by\nthe TSC or are adopted into that organization from outside.\n\nIn the case of adopting existing projects, once the TSC has decided that\nadoption is appropriate, it should seek agreement from the OpenJS Foundation Board\nfor such adoption as it impacts the scope of technical activities of the\nFoundation.\n\nCurrent adjacent projects that are within the TSC's scope of responsibility\ninclude:\n\n* \u003chttps://github.com/nodejs/abi-stable-node\u003e — administration delegated to the API Working Group\n* \u003chttps://github.com/nodejs/abi-stable-node-addon-examples\u003e — administration delegated to the API Working Group\n* \u003chttps://github.com/nodejs/api\u003e — administration delegated to the API Working Group\n* \u003chttps://github.com/nodejs/code-and-learn\u003e\n* \u003chttps://github.com/nodejs/diagnostics\u003e — administration delegated to the Diagnostics Working Group\n* \u003chttps://github.com/nodejs/docs\u003e\n* \u003chttps://github.com/nodejs/education\u003e\n* \u003chttps://github.com/nodejs/email\u003e — administration delegated to the Build Working Group\n* \u003chttps://github.com/nodejs/github-bot\u003e\n* \u003chttps://github.com/nodejs/help\u003e\n* \u003chttps://github.com/nodejs/http\u003e\n* \u003chttps://github.com/nodejs/http2\u003e\n* \u003chttps://github.com/nodejs/installer\u003e\n* \u003chttps://github.com/nodejs/llnode\u003e — administration delegated to the Post Mortem Working Group\n* \u003chttps://github.com/nodejs/nan\u003e — administration delegated to the Addon API Working Group\n* \u003chttps://github.com/nodejs/node-addon-examples\u003e — administration delegated to the Addon API Working Group\n* \u003chttps://github.com/nodejs/node-chakracore\u003e\n* \u003chttps://github.com/nodejs/node-gyp\u003e\n* \u003chttps://github.com/nodejs/node-inspect\u003e — administration delegated to the Diagnostics Working Group\n* \u003chttps://github.com/nodejs/node-report\u003e — administration delegated to the Post Mortem Working Group\n* \u003chttps://github.com/nodejs/nodejs.org\u003e — administration delegated to the Website Working Group\n* \u003chttps://github.com/nodejs/post-mortem\u003e — administration delegated to the Post Mortem Working Group\n* \u003chttps://github.com/nodejs/promises\u003e\n* \u003chttps://github.com/nodejs/readable-stream\u003e — administration delegated to the Streams Working Group\n* \u003chttps://github.com/nodejs/summit\u003e\n* \u003chttps://github.com/nodejs/testing\u003e\n* _And_ various language and resource translation groups under \u003chttps://github.com/nodejs/\u003e\n\n### List of TSC responsibilities\n\nThe TSC exercises autonomy in setting up and maintaining procedures, policies,\nand management and administrative structures as it deems appropriate for the\nmaintenance and operation of these projects and resources.\n\nIncluded in the responsibilities of the TSC are:\n\n* Managing code and documentation creation and changes for the listed projects\n  and resources\n* Setting and maintaining standards covering contributions of code,\n  documentation, and other materials\n* Managing code and binary releases: types, schedules, frequency, delivery\n  mechanisms\n* Making decisions regarding dependencies of the Node.js Core project,\n  including what those dependencies are and how they are bundled with source\n  code and releases\n* Creating new repositories and projects under the _nodejs_ GitHub organization\n  as required\n* Setting overall technical direction for the Node.js Core project, including\n  high-level goals and low-level specifics regarding features and functionality\n* Setting and maintaining appropriate standards for community discourse via the\n  various mediums under TSC control\n* Setting and maintaining governance rules for the conduct and make-up of the\n  TSC, Working Groups and other bodies within the TSC's domain\n\nMany of these responsibilities will be delegated by the TSC to appropriate\nbodies such as the Working Groups.\n\n## TSC members\n\nTSC members are responsible for top-level technical community concerns. The role\nis mostly administrative and is responsible for admitting new Working Groups\nand advocating for any needs in the\ntechnical side of the project to the OpenJS Foundation Board of Directors.\n\nTSC members can nominate new members at any time. Candidates for membership tend\nto be people who have a competency for community management and a high tolerance\nand patience for process minutiae as the TSC delegates most of its\nresponsibilities to other working groups.\n\nA [current list of TSC members](https://github.com/nodejs/node#tsc-technical-steering-committee)\nis maintained in the main Node.js repository.\n\n## YouTube\n\nMany teams/groups post meeting videos to the\n[Node.js YouTube channel][].\n\nAny GitHub team maintainer is allowed `Manager` access to the Google Plus\naccount allowing them to add/manage video content and schedule events\n(live broadcasts).\n\nMembers of the TSC are allowed `Owner` access to the Google Plus account. This\nrole can do all `Manager` activities and add/remove other members from the\nGoogle Plus account.\n\nTo request access, [open an issue](https://github.com/nodejs/TSC/issues/new).\n\n## Strategic initiatives\n\n* [Strategic initiatives](https://github.com/nodejs/node/blob/HEAD/doc/contributing/strategic-initiatives.md)\n\n## Working Groups\n\n* [Working Groups](WORKING_GROUPS.md)\n\n## Policy change proposal process\n\nThe Node.js TSC is chartered to oversee the technical governance of all Working Groups under Node.js. Working Groups have broad powers of\nself-governance.\n\nTo propose a change or addition to policies or processes that are intended to\ncover all Working Groups, a PR should\nbe opened in the `nodejs/TSC` repository.\n\nThe pull request can be labeled `tsc-agenda` to request that it be put on the\nagenda for the next TSC meeting.\n\nThe OpenJS Foundation Board of Directors retains certain rights (especially\nlegal considerations). If the TSC endorses a proposal, they will escalate to the\nOpenJS Foundation Board of Directors when required to do so.\n\nIn some cases, existing individual groups have the right to refuse changes to\ntheir charters. The TSC can not mandate existing working groups alter their\ncharters. If such a situation arises, the TSC may decide to revoke the group's\ncharter.\n\n[Node.js YouTube channel]: https://www.youtube.com/c/nodejs+foundation/\n[TSC Charter]: https://github.com/nodejs/TSC/blob/master/TSC-Charter.md\n[deps]: https://github.com/nodejs/node/tree/main/deps\n[tools]: https://github.com/nodejs/node/tree/main/tools\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnodejs%2Ftsc","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fnodejs%2Ftsc","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnodejs%2Ftsc/lists"}