Node.js Core Working Groups
Node.js Core Working Groups are autonomous projects created by the Technical Steering Committee (TSC).
Working Groups can be formed at any time but must be ratified by the TSC. Once formed the work defined in the Working Group charter is the responsibility of the WG rather than the TSC.
It is important that Working Groups are not formed pre-maturely. Working Groups are not formed to begin a set of tasks but instead are formed once that work is already underway and the contributors think it would benefit from being done as an autonomous project.
If the work defined in a Working Group's charter is complete, the charter should be revoked.
A Working Group's charter can be revoked either by consent of the Working Group's members or by a TSC vote. Once revoked, any future work that arises becomes the responsibility of the TSC.
Joining a WG
To find out how to join a working group, consult the GOVERNANCE.md in the working group's repository.
Starting A Core Working Group
A Working Group is established by first defining a charter that can be ratified by the TSC. A charter is a statement of purpose, a list of responsibilities and a list of initial membership.
A working group needs 3 initial members. These should be individuals already undertaking the work described in the charter.
The list of responsibilities should be specific. Once established, these responsibilities are no longer governed by the TSC and therefore should not be broad or subjective. The only recourse the TSC has over the working group is to revoke the entire charter and take on the work previously done by the working group themselves.
If the responsibilities described in the charter are currently undertaken by another WG then the charter will additionally have to be ratified by that WG.
You can submit the WG charter for ratification by sending a Pull Request to this document, which adds it to the list of current Working Groups. Once ratified the list of members should be maintained in the Working Group's README.
Once the TSC ratifies a charter the WG inherits the following documentation for governance, contribution, conduct and an MIT LICENSE. The WG is free to change these documents through their own governance process, hence the term "bootstrap."
### *[insert WG name]* Working Group The Node.js *[insert WG name]* is jointly governed by a Working Group (WG) that is responsible for high-level guidance of the project. The WG has final authority over this project including: * Technical direction * Project governance and process (including this policy) * Contribution policy * GitHub repository hosting * Conduct guidelines * Maintaining the list of additional Collaborators For the current list of WG members, see the project [README.md](./README.md#current-project-team-members). ### Collaborators The *[insert WG name]* GitHub repository is maintained by the WG and additional Collaborators who are added by the WG on an ongoing basis. Individuals making significant and valuable contributions are made Collaborators and given commit-access to the project. These individuals are identified by the WG and their addition as Collaborators is discussed during the weekly WG meeting. _Note:_ If you make a significant contribution and are not considered for commit-access log an issue or contact a WG member directly and it will be brought up in the next WG meeting. Modifications of the contents of the *[insert WG repo]* repository are made on a collaborative basis. Anybody with a GitHub account may propose a modification via pull request and it will be considered by the project Collaborators. All pull requests must be reviewed and accepted by a Collaborator with sufficient expertise who is able to take full responsibility for the change. In the case of pull requests proposed by an existing Collaborator, an additional Collaborator is required for sign-off. Consensus should be sought if additional Collaborators participate and there is disagreement around a particular modification. See _Consensus Seeking Process_ below for further detail on the consensus model used for governance. Collaborators may opt to elevate significant or controversial modifications, or modifications that have not found consensus to the WG for discussion by assigning the ***WG-agenda*** tag to a pull request or issue. The WG should serve as the final arbiter where required. For the current list of Collaborators, see the project [README.md](./README.md#current-project-team-members). ### WG Membership WG seats are not time-limited. There is no fixed size of the WG. However, the expected target is between 6 and 12, to ensure adequate coverage of important areas of expertise, balanced with the ability to make decisions efficiently. There is no specific set of requirements or qualifications for WG membership beyond these rules. The WG may add additional members to the WG by unanimous consensus. A WG member may be removed from the WG by voluntary resignation, or by unanimous consensus of all other WG members. Changes to WG membership should be posted in the agenda, and may be suggested as any other agenda item (see "WG Meetings" below). If an addition or removal is proposed during a meeting, and the full WG is not in attendance to participate, then the addition or removal is added to the agenda for the subsequent meeting. This is to ensure that all members are given the opportunity to participate in all membership decisions. If a WG member is unable to attend a meeting where a planned membership decision is being made, then their consent is assumed. No more than 1/3 of the WG members may be affiliated with the same employer. If removal or resignation of a WG member, or a change of employment by a WG member, creates a situation where more than 1/3 of the WG membership shares an employer, then the situation must be immediately remedied by the resignation or removal of one or more WG members affiliated with the over-represented employer(s). ### WG Meetings The WG meets weekly on a Google Hangout On Air. A designated moderator approved by the WG runs the meeting. Each meeting should be published to YouTube. Items are added to the WG agenda that are considered contentious or are modifications of governance, contribution policy, WG membership, or release process. The intention of the agenda is not to approve or review all patches; that should happen continuously on GitHub and be handled by the larger group of Collaborators. Any community member or contributor can ask that something be added to the next meeting's agenda by logging a GitHub Issue. Any Collaborator, WG member or the moderator can add the item to the agenda by adding the ***WG-agenda*** tag to the issue. Prior to each WG meeting the moderator will share the Agenda with members of the WG. WG members can add any items they like to the agenda at the beginning of each meeting. The moderator and the WG cannot veto or remove items. The WG may invite persons or representatives from certain projects to participate in a non-voting capacity. The moderator is responsible for summarizing the discussion of each agenda item and sends it as a pull request after the meeting. ### Consensus Seeking Process The WG follows a [Consensus Seeking] decision-making model. When an agenda item has appeared to reach a consensus the moderator will ask "Does anyone object?" as a final call for dissent from the consensus. If an agenda item cannot reach a consensus a WG member can call for either a closing vote or a vote to table the issue to the next meeting. The call for a vote must be seconded by a majority of the WG or else the discussion will continue. Simple majority wins. Note that changes to WG membership require unanimous consensus. See "WG Membership" above. <a id="developers-certificate-of-origin"></a> ## Developer's Certificate of Origin 1.1 *Note*: The DCO is mandatory for all Node.js Foundation projects. By making a contribution to this project, I certify that: * (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or * (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or * (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. * (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved. ### Moderation Policy The [Node.js Moderation Policy] applies to this WG. ### Code of Conduct The [Node.js Code of Conduct] applies to this WG. [Node.js Code of Conduct]: https://github.com/nodejs/TSC/blob/master/CODE_OF_CONDUCT.md [Node.js Moderation Policy]: https://github.com/nodejs/TSC/blob/master/Moderation-Policy.md
Current Working Groups
The website Working Group's purpose is to build and maintain a public website for the Node.js project.
- Developing and maintaining a build and automation system for nodejs.org.
- Ensuring the site is regularly updated with changes made to Node.js, like releases and features.
- Fostering and enabling a community of translators.
The Streams Working Group is dedicated to the support and improvement of the Streams API as used in Node.js and the npm ecosystem. We seek to create a composable API that solves the problem of representing multiple occurrences of an event over time in a humane, low-overhead fashion. Improvements to the API will be driven by the needs of the ecosystem; interoperability and backwards compatibility with other solutions and prior versions are paramount in importance.
- Addressing stream issues on the Node.js issue tracker.
- Authoring and editing stream documentation within the Node.js project.
- Reviewing changes to stream subclasses within the Node.js project.
- Redirecting changes to streams from the Node.js project to this project.
- Assisting in the implementation of stream providers within Node.js.
- Recommending versions of
readable-streamto be included in Node.js.
- Messaging about the future of streams to give the community advance notice of changes.
The Build Working Group's purpose is to create and maintain a distributed automation infrastructure.
- Producing packages for all target platforms.
- Running tests.
- Running performance testing and comparisons.
- Creating and managing build-containers.
- Collaborating with V8 to integrate
- Collaborating with V8 to integrate
- Collaborating with Core to refine
- Maintaining and improving OS trace system integration (e.g. ETW, LTTNG, dtrace).
- Documenting diagnostic capabilities and APIs in Node.js and its components.
- Exploring opportunities and gaps, discussing feature requests, and addressing conflicts in Node.js diagnostics.
- Fostering an ecosystem of diagnostics tools for Node.js.
- Defining and adding interfaces/APIs in order to allow dumps to be generated when needed.
- Defining and adding common structures to the dumps generated in order to support tools that want to introspect those dumps.
The i18n Working Groups handle more than just translations. They are endpoints for community members to collaborate with each other in their language of choice.
Each team is organized around a common spoken language. Each language community might then produce multiple localizations for various project resources.
- Translating any Node.js materials they believe are relevant to their community.
- Reviewing processes for keeping translations up to date and of high quality.
- Managing and monitoring social media channels in their language.
- Promoting Node.js speakers for meetups and conferences in their language.
Each language community maintains its own membership.
- nodejs-ar - Arabic (اللغة العربية)
- nodejs-bg - Bulgarian (български език)
- nodejs-bn - Bengali (বাংলা)
- nodejs-zh-CN - Chinese (中文)
- nodejs-cs - Czech (Český Jazyk)
- nodejs-da - Danish (Dansk)
- nodejs-de - German (Deutsch)
- nodejs-el - Greek (Ελληνικά)
- nodejs-es - Spanish (Español)
- nodejs-fa - Persian (فارسی)
- nodejs-fi - Finnish (Suomi)
- nodejs-fr - French (Français)
- nodejs-he - Hebrew (עברית)
- nodejs-hi - Hindi (फिजी बात)
- nodejs-hu - Hungarian (Magyar)
- nodejs-id - Indonesian (Bahasa Indonesia)
- nodejs-it - Italian (Italiano)
- nodejs-ja - Japanese (日本語)
- nodejs-ka - Georgian (ქართული)
- nodejs-ko - Korean (조선말)
- nodejs-mk - Macedonian (Mакедонски)
- nodejs-ms - Malay (بهاس ملايو)
- nodejs-nl - Dutch (Nederlands)
- nodejs-no - Norwegian (Norsk)
- nodejs-pl - Polish (Język Polski)
- nodejs-pt - Portuguese (Português)
- nodejs-ro - Romanian (Română)
- nodejs-ru - Russian (Русский)
- nodejs-sv - Swedish (Svenska)
- nodejs-ta - Tamil (தமிழ்)
- nodejs-tr - Turkish (Türkçe)
- nodejs-zh-TW - Taiwanese (Hō-ló)
- nodejs-uk - Ukrainian (Українська)
- nodejs-vi - Vietnamese (Tiếng Việtnam)
The Docker Working Group's purpose is to build, maintain, and improve official Docker images for the Node.js project.
- Keeping the official Docker images updated in line with new Node.js releases.
- Decide and implement image improvements and/or fixes.
- Maintain and improve the images' documentation.
The Addon API Working Group is responsible for maintaining the NAN project and corresponding nan package in npm. The NAN project makes available an abstraction layer for native add-on authors for Node.js, assisting in the writing of code that is compatible with many actively used versions of Node.js, V8 and libuv.
- Maintaining the NAN GitHub repository, including code, issues and documentation.
- Maintaining the addon-examples GitHub repository, including code, issues and documentation.
- Maintaining the C++ Addon API within the Node.js project, in subordination to the Node.js TSC.
- Maintaining the Addon documentation within the Node.js project, in subordination to the Node.js TSC.
- Maintaining the nan package in npm, releasing new versions as appropriate.
- Messaging about the future of the Node.js and NAN interface to give the community advance notice of changes.
The current members can be found in their README.
The purpose of the Benchmark Working Group is to gain consensus on an agreed set of benchmarks that can be used to:
- track and evangelize performance gains made between Node.js releases
- avoid performance regressions between releases
- Identifying 1 or more benchmarks that reflect customer usage. Likely will need more than one to cover typical Node.js use cases including low-latency and high concurrency
- Working to get community consensus on the list chosen
- Adding regular execution of chosen benchmarks to Node.js builds
- Tracking/publicizing performance between builds/releases
The Release Working Group manages the release process for Node.js.
- Define the release process.
- Define the content of releases.
- Generate and create releases.
- Test Releases.
- Manage the Long Term Support and Current branches including backporting changes to these branches.
- Define the policy for what gets backported to release streams.
The Security Working Group manages all aspects and processes linked to Node.js security.
- Define and maintain security policies and procedures for:
- the core Node.js project
- other projects maintained by the Node.js Technical Steering Committee (TSC).
- Work with the Node Security Platform to bring community vulnerability data into the foundation as a shared asset.
- Ensure the vulnerability data is updated in an efficient and timely manner. For example, ensuring there are well-documented processes for reporting vulnerabilities in community modules.
- Review and recommend processes for handling of security reports (but not the actual administration of security reports, which are reviewed by a group of people directly delegated to by the TSC).
- Define and maintain policies and procedures for the coordination of security concerns within the external Node.js open source ecosystem.
- Offer help to npm package maintainers to fix high-impact security bugs.
- Maintain and make available data on disclosed security vulnerabilities in:
- the core Node.js project
- other projects maintained by the Node.js Foundation technical group
- the external Node.js open source ecosystem
- Promote the improvement of security practices within the Node.js ecosystem.
- Recommend security improvements for the core Node.js project.
- Facilitate and promote the expansion of a healthy security service and product provider ecosystem.