The Node.js Web Team (@nodejs/web) is a team in the Node.js Project that is composed by a set of subteams. Each containing specific responsibilities and goals.
Any website change that expresses a position about a global event or group of people requires explicit
TSC
approval. This can be obtained by pinging @nodejs/tsc and receive no objections after seven days,
or by sending an email to tsc@iojs.org and receive at least one approval and no objections after seven days.
The Node.js Website Team is responsible for the day-to-day technical development of the Node.js Website. This is primarily the development of the website itself, adding new features, pages and components, but also fixing any security issues in the website code, handling operational maintenance, and so on.
The maintainers on the Node.js Website Team are responsible for steering the technical direction of the Node.js Website, and reserve the right to make final decisions on any issues or pull requests, in line with the Contribution Guidelines, Collaborator Guidelines, the Code of Conduct and the overall Governance premises of the Node.js project.
Members of this team are nominated through the guidelines provided in the Contributing Guidelines within the nodejs.org repository. After a passed nomination, members should submit a PR to add themselves to the list of current members, shown within MEMBERS.md.
The Node.js Web Infra Team is responsible for maintaining the Infrastructure relating to Node.js's Web Presence. The Node.js Web Infra team has the responsibilities of:
- Maintaining CI/CD pipelines related to Web Infrastructure
- Maintaining our Infrastructure Providers*
- Have technical ownership on best-standards and best-practices for our Web Infrastructure (such as Web Frameworks that we use)
Web Infra Team members should have access to maintain the services mentioned above.
Members of this team are nominated either by the Node.js Technical Steering Committee (TSC) or the Node.js Build WG and follow the guidelines provided in the Collaborator Guidelines of the Node.js Build WG. Current members of the Node.js Web Infra Team may also nominate individuals.
* This team has access to infrastructure providers directly related to the Website only, such as Vercel. Other providers that are shared beyond the Website may be controlled by other teams (for example, the Node.js Build WG owns Cloudflare).
When considering new members, approvers are primarily concerned with competence and trust. The language within the Build WG pertaining to competence and trust applies here. The following is repeated, for emphasis:
Important
Please be aware of the fact that the Web-Infra team is usually invisible to the Node.js project when things go well, but highly visible when things don't go well. Downtime of important resources can have a very wide impact, not just for Node.js open source contributors but for very large sections of the Node.js user ecosystem. Security breaches could have devastating consequences and these all reflect on the project.
As seen above, the different teams under the Node.js Web Team umbrella are responsible for having the oversight on different aspects of Node.js's Web-related projects. However, it is important to note that the Node.js Web Team is not a set of siloed teams, but rather a set of teams that work together to achieve the same goal: Providing the best Web Experience for Node.js.
Following this line of thought, the Web Infra Team is responsible for the technical aspects of the Node.js Website (Infrastructure, Framework, CI/CD, etc); The Website Team is responsible for the day-to-day development of the Node.js Website.
But above all, the Web Team should work together to better the Web Experience for Node.js, aiming to provide the best experience for Node.js users.
