Welcome! You've come to the right place. You can jump right in by going to the working group guides below. You can accelerate getting started in any of these working groups by being introduced to a member of the working group who is knowledgable in the work you'd like to tackle. Context to approaching problems is important and these introductions can save you time working on something the collaborators have already tackled. If you'd like an introduction, file an issue with
- what you'd like to work on or the challenge you're facing
- the working group (if known)
and we'll label your request as intro requested. A collaborator will facilitate this for you.
- Website WG
The Website Working Group is primarily concerned with the code and overall structure of the Node.js website. - Streams WG
The Streams Working Group is dedicated to the support and improvement of the Streams API as used in Node.js and the npm ecosystem. - Build WG
The Node.js Build Working Group maintains and controls infrastructure used for continuous integration (CI), releases, benchmarks, web hosting (of nodejs.org and other Node.js web properties) and more. - i18n
The i18n Working Groups handle more than just translations. Each working group is an endpoint for community members to collaborate with each other in their language of choice. - Docker WG
The Docker Working Group's purpose is to build, maintain, and improve official Docker images for the Node.js project. - Benchmarking WG
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 and avoid performance regressions between releases. - citgm
citgm is a tool for pulling down an arbitrary module from npm and testing it using a specific version of the node runtime. The Node.js project uses citgm to smoketest releases and controversial changes. - Diagnostics WG
Diagnostics ensures Node.js provides a set of comprehensive, documented, extensible diagnostic protocols, formats, and APIs to enable tool vendors to provide reliable diagnostic tools for Node.js including tracing, profiling, heap and memory analysis, and step debugging. - Community Committee
The Community Committee tackles challenges within the Node.js project that require the many roles outside of code contribution vital to sustaining a healthy open source project. - Release WG
The Release Working Group manages the release process for Node.js. - Security
The Security Working Group's purpose is to achieve the highest level of security for Node.js and community modules.