diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index 9117946..2f84952 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -1,2 +1 @@ * @nodejs/web-admins -GOVERNANCE.md @nodejs/tsc \ No newline at end of file diff --git a/.github/scripts/inactive-collaborator-report.mjs b/.github/scripts/inactive-collaborator-report.mjs index 9b32a8b..ace4d73 100644 --- a/.github/scripts/inactive-collaborator-report.mjs +++ b/.github/scripts/inactive-collaborator-report.mjs @@ -1,8 +1,8 @@ import { readFile } from "node:fs/promises"; const CONFIG = { - FILE: "MEMBERS.md", - HEADER: "## Node.js Website Team (`@nodejs/nodejs-website`)", + FILE: "README.md", + HEADER: "### Node.js Website Team (`@nodejs/nodejs-website`)", INACTIVE_MONTHS: 12, ISSUE_TITLE: "Inactive Collaborator Report", ISSUE_LABELS: ["meta", "inactive-collaborator-report"], diff --git a/GOVERNANCE.md b/GOVERNANCE.md index ac840af..2c6e5f2 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -1,6 +1,6 @@ -# Node.js Web Team Governance +# Node.js Web WG Governance -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. +The Node.js Web WG (`@nodejs/web`) is a Working Group in the Node.js Project composed of a set of subteams, each with specific responsibilities and goals. ### TSC Oversight @@ -9,13 +9,17 @@ Any website change that expresses a position about a global event or group of pe 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. +### OpenJS Oversight and Content Input + +Website content including, but not limited to, the [blog](https://nodejs.org/en/blog), [about](https://nodejs.org/en/about), and [partner](https://nodejs.org/en/about/partners) pages are governed by the [content vs. code](https://github.com/nodejs/nodejs.org/blob/main/docs/content-vs-code.md) guidance. Additionally, OpenJS Foundation requests are always honored, such as including project and foundation links in the footer. + ### Node.js Website Team (`@nodejs/nodejs-website`) 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](https://github.com/nodejs/nodejs.org/blob/main/CONTRIBUTING.md#becoming-a-collaborator) within the [nodejs.org](https://github.com/nodejs/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](https://github.com/nodejs/web-team/blob/main/MEMBERS.md). +Members of this team are nominated through the guidelines provided in the [Contributing Guidelines](https://github.com/nodejs/nodejs.org/blob/main/CONTRIBUTING.md#becoming-a-collaborator) within the [nodejs.org](https://github.com/nodejs/nodejs.org) repository. After a passed nomination, members should submit a PR to add themselves to the list of current members, shown within the [README.md](https://github.com/nodejs/web-team/blob/main/README.md#members). ### Node.js Web Infra Team (`@nodejs/web-infra`) @@ -27,7 +31,7 @@ The Node.js Web Infra Team is responsible for maintaining the Infrastructure rel 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. +Members of this team are nominated by current members of the Node.js Web Infra Team or by the Web Working Group, and follow the guidelines provided in the Collaborator Guidelines of the Node.js Build WG. Nominations are decided by the Working Group, as described in [WG Membership](https://github.com/nodejs/web-team/blob/main/README.md#wg-membership). \* 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). @@ -52,10 +56,10 @@ In other words, if someone other than the author requests fast-track on a PR, th While there are special exceptions that require bypassing this policy, all unorthodox merges should have proper justification in writing in GitHub and/or Slack. -## The Interoperability of the Node.js Web Team +## The Interoperability of the Node.js Web WG -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. +As seen above, the different teams under the Node.js Web WG 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 WG 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. +But above all, the Web WG should work together to better the Web Experience for Node.js, aiming to provide the best experience for Node.js users. diff --git a/MEMBERS.md b/MEMBERS.md deleted file mode 100644 index a4d4fe3..0000000 --- a/MEMBERS.md +++ /dev/null @@ -1,34 +0,0 @@ -# Node.js Web Team Members - -## Node.js Website Team (`@nodejs/nodejs-website`) - -- [@araujogui](https://github.com/araujogui) - **Guilherme Araújo** (he/him) -- [@AugustinMauroy](https://github.com/AugustinMauroy) - **Augustin Mauroy** (he/him) -- [@avivkeller](https://github.com/avivkeller) - **Aviv Keller** (he/him) -- [@aymen94](https://github.com/aymen94) - **Aymen Naghmouchi** -- [@benhalverson](https://github.com/benhalverson) - **Ben Halverson** (he/him) -- [@bjohansebas](https://github.com/bjohansebas) - **Sebastian Beltran** -- [@bmuenzenmeyer](https://github.com/bmuenzenmeyer) - **Brian Muenzenmeyer** (he/him) -- [@bnb](https://github.com/bnb) - **Tierney Cyren** (they/them) -- [@canerakdas](https://github.com/canerakdas) - **Caner Akdas** -- [@dario-piotrowicz](https://github.com/dario-piotrowicz) - **Dario Piotrowicz** -- [@Harkunwar](https://github.com/Harkunwar) - **Harkunwar Kochar** (he/him) -- [@manishprivet](https://github.com/manishprivet) - **Manish Kumar** (he/him) -- [@mikeesto](https://github.com/mikeesto) - **Michael Esteban** (he/him) -- [@ovflowd](https://github.com/ovflowd) - **Claudio Wunder** (they/them) - -## Node.js Web Infra Team (`@nodejs/web-infra`) - -- [@avivkeller](https://github.com/avivkeller) - **Aviv Keller** <> (he/him) -- [@bmuenzenmeyer](https://github.com/bmuenzenmeyer) - **Brian Muenzenmeyer** <> (he/him) -- [@canerakdas](https://github.com/canerakdas) - **Caner Akdas** <> (he/him) -- [@flakey5](https://github.com/flakey5) - **flakey5** <> (she/her) -- [@MattIPv4](https://github.com/MattIPv4) - **Matt Cowley** <> (he/him) -- [@MoLow](https://github.com/MoLow) - **Moshe Atlow** <> (he/him) -- [@ovflowd](https://github.com/ovflowd) - **Claudio Wunder** <> (they/them) - -## Node.js Web Admins Team (`@nodejs/web-admins`) - -- [@bmuenzenmeyer](https://github.com/bmuenzenmeyer) - **Brian Muenzenmeyer** (he/him) -- [@MattIPv4](https://github.com/MattIPv4) - **Matt Cowley** (he/him) -- [@ovflowd](https://github.com/ovflowd) - **Claudio Wunder** (they/them) diff --git a/README.md b/README.md index 597d0a0..22a232e 100644 --- a/README.md +++ b/README.md @@ -1,15 +1,251 @@ -# Node.js Web Team Governance Repository +# Node.js Web Working Group -This repository contains the governance documentation, workflows, and shared resources for the Node.js Web Team ([`@nodejs/web`](https://github.com/orgs/nodejs/teams/web)) and its subteams. +The Node.js Web Working Group ([`@nodejs/web`](https://github.com/orgs/nodejs/teams/web)) +is a [Node.js Core Working Group][], chartered by the +[Technical Steering Committee (TSC)][]. -## Sub-Team Structure +This repository contains the charter, governance documentation, workflows, and +shared resources for the Working Group and its subteams. -The Node.js Web Team consists of two specialized subteams: +The WG is responsible for high-level guidance of the Node.js web presence and has +final authority over the work described in the charter below, and over the +following teams: + +- [`@nodejs/web`](https://github.com/orgs/nodejs/teams/web) +- [`@nodejs/nodejs-website`](https://github.com/orgs/nodejs/teams/nodejs-website) +- [`@nodejs/web-infra`](https://github.com/orgs/nodejs/teams/web-infra) +- [`@nodejs/web-admins`](https://github.com/orgs/nodejs/teams/web-admins) + +For the current list of WG members, see [Members](#members). + +## Charter + +The Web Working Group is responsible for the Node.js project's web presence: the +development, operation, and security of nodejs.org and the infrastructure that +serves it. + +Responsibilities include: + +- Technical direction and day-to-day development of the Node.js website and its + supporting projects, including `nodejs/nodejs.org`, `nodejs/learn`, and + `nodejs/doc-kit`. +- Operating and maintaining the infrastructure serving the Node.js web presence, + including CI/CD pipelines, `nodejs/website-cloudflare-worker`, + `nodejs/release-cloudflare-worker`, and `nodejs/discord-status-worker`. +- Managing access to, and administration of, the third-party services used to run + the Node.js web presence, as enumerated in the Working Group's + [PERMISSIONS.md](PERMISSIONS.md). +- Responding to availability and security incidents affecting the Node.js web + presence, per the Working Group's + [incident response plan](INCIDENT_RESPONSE_PLAN.md). +- Maintaining localization tooling and workflows for the Node.js website. +- Project governance and process for the Working Group, including this policy, its + contribution policy, and its permissions model. +- Managing the membership of `@nodejs/web` and its subteams, including + `@nodejs/nodejs-website`, `@nodejs/web-infra`, and `@nodejs/web-admins`. +- Overseeing repositories within the Working Group's scope (creating, moving, + archiving, removing) and their maintainer teams. + +### Outside the Charter + +- **Editorial positions.** Chartering does not change the + [TSC Oversight](GOVERNANCE.md#tsc-oversight) clause described about global positions or events. +- **Foundation, Partner, Marketing, or Collaborator content.** Chartering does not change [content input](GOVERNANCE.md#openjs-oversight-and-content-input) from stakeholders that have [content vs. code][] scope. +- **Shared infrastructure.** Cloudflare is owned by the [Build WG][]; the Web WG + holds scoped access only. Changes to that boundary require agreement from the + Build WG. +- **Anything not listed above.** Work outside these responsibilities remains with + the TSC. + +Within the charter, the TSC's only recourse over a Working Group is to revoke its +charter. + +## Working Group Structure + +The Working Group consists of three specialized subteams: - **Website Team** ([`@nodejs/nodejs-website`](https://github.com/orgs/nodejs/teams/nodejs-website)) - Day-to-day website development - **Web Infra Team** ([`@nodejs/web-infra`](https://github.com/orgs/nodejs/teams/web-infra)) - Infrastructure and CI/CD -_There is also the **Web Admins Team** ([`@nodejs/web-admins`](https://github.com/orgs/nodejs/teams/web-admins)), which is responsible for administrative operations relating to the Web Team._ +_There is also the **Web Admins Team** ([`@nodejs/web-admins`](https://github.com/orgs/nodejs/teams/web-admins)), which is responsible for administrative operations relating to the Working Group._ + +For detailed information about each team's responsibilities, see +[GOVERNANCE.md](GOVERNANCE.md). + +## Members + +### Node.js Website Team (`@nodejs/nodejs-website`) + +- [@araujogui](https://github.com/araujogui) - **Guilherme Araújo** (he/him) +- [@AugustinMauroy](https://github.com/AugustinMauroy) - **Augustin Mauroy** (he/him) +- [@avivkeller](https://github.com/avivkeller) - **Aviv Keller** (he/him) +- [@aymen94](https://github.com/aymen94) - **Aymen Naghmouchi** +- [@benhalverson](https://github.com/benhalverson) - **Ben Halverson** (he/him) +- [@bjohansebas](https://github.com/bjohansebas) - **Sebastian Beltran** +- [@bmuenzenmeyer](https://github.com/bmuenzenmeyer) - **Brian Muenzenmeyer** (he/him) +- [@bnb](https://github.com/bnb) - **Tierney Cyren** (they/them) +- [@canerakdas](https://github.com/canerakdas) - **Caner Akdas** +- [@dario-piotrowicz](https://github.com/dario-piotrowicz) - **Dario Piotrowicz** +- [@Harkunwar](https://github.com/Harkunwar) - **Harkunwar Kochar** (he/him) +- [@manishprivet](https://github.com/manishprivet) - **Manish Kumar** (he/him) +- [@mikeesto](https://github.com/mikeesto) - **Michael Esteban** (he/him) +- [@ovflowd](https://github.com/ovflowd) - **Claudio Wunder** (they/them) + +### Node.js Web Infra Team (`@nodejs/web-infra`) + +- [@avivkeller](https://github.com/avivkeller) - **Aviv Keller** <> (he/him) +- [@bmuenzenmeyer](https://github.com/bmuenzenmeyer) - **Brian Muenzenmeyer** <> (he/him) +- [@canerakdas](https://github.com/canerakdas) - **Caner Akdas** <> (he/him) +- [@flakey5](https://github.com/flakey5) - **flakey5** <> (she/her) +- [@MattIPv4](https://github.com/MattIPv4) - **Matt Cowley** <> (he/him) +- [@MoLow](https://github.com/MoLow) - **Moshe Atlow** <> (he/him) +- [@ovflowd](https://github.com/ovflowd) - **Claudio Wunder** <> (they/them) + +### Node.js Web Admins Team (`@nodejs/web-admins`) + +- [@bmuenzenmeyer](https://github.com/bmuenzenmeyer) - **Brian Muenzenmeyer** (he/him) +- [@MattIPv4](https://github.com/MattIPv4) - **Matt Cowley** (he/him) +- [@ovflowd](https://github.com/ovflowd) - **Claudio Wunder** (they/them) + +## Collaborators + +The repositories within the WG's scope are maintained by the WG and additional +Collaborators who are added by the WG on an ongoing basis. The access each team +holds is listed in [PERMISSIONS.md](PERMISSIONS.md). + +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 via pull requests and at WG meetings. Members of +`@nodejs/nodejs-website` are nominated through the [Contributing Guidelines][] in +the [nodejs.org][] repository. + +_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 at the next WG meeting. + +Modifications of the contents of the repositories within the WG's scope 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. Pull requests are also subject to the +[Pull Request Policies](GOVERNANCE.md#pull-request-policies) in GOVERNANCE.md. + +Collaborators may opt to elevate significant or controversial modifications, or +modifications that have not found consensus, to the WG for discussion by applying +the `web-agenda` label to a pull request or issue. The WG should serve as the +final arbiter where required. + +For the current list of Collaborators, see [Members](#members) above. + +## WG Membership + +WG seats are not time-limited. There is no fixed size of the WG. + +Membership of `@nodejs/web` and its subteams is determined by the Working Group. +Any WG member may nominate an individual, following the process for each subteam +described in [GOVERNANCE.md](GOVERNANCE.md). Nominations are decided by the active +members of the WG, per the _Consensus Seeking Process_ below. + +A WG member may be removed from the WG by voluntary resignation, or by consensus +of the other active WG members. The WG runs an +[inactive collaborator report](.github/workflows/inactive-collaborator-report.yml) +to identify members who may no longer be active. An emeritus member may rejoin the +WG following consensus from the current WG. + +Changes to WG membership should be posted in the agenda, and may be suggested as +any other agenda item (see [meetings/README.md](meetings/README.md)). + +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. + +When considering new members for `@nodejs/web-infra` and `@nodejs/web-admins`, +approvers are primarily concerned with **competence** and **trust**, per the +[language within the Build WG pertaining to competence and trust][build-membership] +and as stated in [GOVERNANCE.md](GOVERNANCE.md#nodejs-web-infra-team-nodejsweb-infra). + +## Special Access Requests + +The Working Group can grant access to the resources it manages to people who are +not WG members. Examples include translators working on a single language in +Crowdin, and contributors who need scoped access to debug a specific problem. + +Requests are made by opening an issue in this repository, and are decided by the +WG. Special access is split into two categories: + +- **Ongoing access** is granted where the need is continuing, such as a translator + maintaining a language. It is reviewed alongside the WG's own membership. +- **Temporary access** is granted for a defined piece of work, and is revoked once + that work is complete. + +Granted access is recorded in [PERMISSIONS.md](PERMISSIONS.md). Access to services +the WG does not own remains subject to the owning team; Cloudflare access, for +example, is granted by the [Build WG][]. + +## WG Meetings + +The WG's meeting schedule, moderation, agenda, and participation process are +described in [meetings/README.md](meetings/README.md). + +Items are added to the WG agenda that are considered contentious or are +modifications of governance, contribution policy, WG membership, or this charter. + +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. + +The moderator is responsible for summarizing the discussion of each agenda item +and sends it as a pull request to [meetings/](meetings) 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. + +Changes to WG membership follow this same process. See "WG Membership" above. + +## Moderation Policy + +The [Node.js Moderation Policy][] applies to this WG. + +## Code of Conduct + +The [Node.js Code of Conduct][] applies to this WG. + +## In This Repository + +| Document | Contents | +| ------------------------------------------------------ | -------------------------------------------------------------- | +| [GOVERNANCE.md](GOVERNANCE.md) | Subteam responsibilities, TSC oversight, pull request policies | +| [PERMISSIONS.md](PERMISSIONS.md) | Repository, service, and token access held by each team | +| [SECURITY.md](SECURITY.md) | How to report a security issue | +| [INCIDENT_RESPONSE_PLAN.md](INCIDENT_RESPONSE_PLAN.md) | Incident classification, response, and postmortem process | +| [meetings/](meetings) | Meeting process and published minutes | +| [onboarding/](onboarding) | Onboarding material for new members | -For detailed information about each team's responsibilities, see [GOVERNANCE.md](GOVERNANCE.md). -For current team membership, see [MEMBERS.md](MEMBERS.md). +[Build WG]: https://github.com/nodejs/build +[Consensus Seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making +[Contributing Guidelines]: https://github.com/nodejs/nodejs.org/blob/main/CONTRIBUTING.md#becoming-a-collaborator +[Node.js Code of Conduct]: https://github.com/nodejs/TSC/blob/main/CODE_OF_CONDUCT.md +[Node.js Core Working Group]: https://github.com/nodejs/TSC/blob/main/WORKING_GROUPS.md +[Node.js Moderation Policy]: https://github.com/nodejs/TSC/blob/main/Moderation-Policy.md +[Technical Steering Committee (TSC)]: https://github.com/nodejs/TSC/blob/main/TSC-Charter.md +[WORKING_GROUPS.md]: https://github.com/nodejs/TSC/blob/main/WORKING_GROUPS.md#web +[build-membership]: https://github.com/nodejs/build/blob/main/GOVERNANCE.md#wg-membership +[content vs. code]: https://github.com/nodejs/nodejs.org/blob/main/docs/content-vs-code.md +[nodejs.org]: https://github.com/nodejs/nodejs.org diff --git a/SECURITY.md b/SECURITY.md index 5510be3..73fa212 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -1,12 +1,12 @@ # Security Policy -This document outlines the security policy for the Node.js Web Team repositories and infrastructure. +This document outlines the security policy for the Node.js Web WG repositories and infrastructure. ## Reporting Security Vulnerabilities -The Node.js Web Team follows the security policies and procedures of the Node.js project. +The Node.js Web WG follows the security policies and procedures of the Node.js project. -For reporting security vulnerabilities in any Node.js Web Team repository or infrastructure, please refer to the official Node.js org security policy: +For reporting security vulnerabilities in any Node.js Web WG repository or infrastructure, please refer to the official Node.js org security policy: **[https://github.com/nodejs/nodejs.org/blob/main/SECURITY.md](https://github.com/nodejs/nodejs.org/blob/main/SECURITY.md)** diff --git a/meetings/README.md b/meetings/README.md index 0729aae..c4e648d 100644 --- a/meetings/README.md +++ b/meetings/README.md @@ -1,14 +1,14 @@ -# Web Team Meetings +# Web WG Meetings -This document outlines the process for the Node.js Web Team meetings. +This document outlines the process for the Node.js Web WG meetings. ## Meeting Schedule -The Web Team holds meetings every 4 weeks to discuss and align on key topics related to Node.js web properties. These meetings help move initiatives forward more efficiently than asynchronous communication alone. +The Web WG holds meetings every 4 weeks to discuss and align on key topics related to Node.js web properties. These meetings help move initiatives forward more efficiently than asynchronous communication alone. For exact dates and times, refer to the [Node.js Calendar](https://nodejs.org/calendar). -In rare cases, a Web Team member may call for an additional meeting outside the regular monthly schedule if there are urgent matters that cannot wait until the next scheduled meeting. All other meeting procedures still apply. +In rare cases, a Web WG member may call for an additional meeting outside the regular monthly schedule if there are urgent matters that cannot wait until the next scheduled meeting. All other meeting procedures still apply. ## Meeting Types @@ -42,7 +42,7 @@ Each meeting is led by a designated moderator who is responsible for: - Ensuring meeting notes are taken and shared - Facilitating decision-making when consensus is needed -For regularly scheduled monthly meetings, the moderator is typically a Web Admin. For exceptional meetings called outside the regular schedule, the Web Team member who called the meeting, or a chosen delegate, serves as the moderator. +For regularly scheduled monthly meetings, the moderator is typically a Web Admin. For exceptional meetings called outside the regular schedule, the Web WG member who called the meeting, or a chosen delegate, serves as the moderator. ## Agenda Items @@ -55,12 +55,12 @@ Any community member or contributor can request items to be added to the meeting The agenda is not intended to review or approve all patches; that should happen continuously on GitHub and be handled by the larger group of Collaborators. -At the start of each meeting, the moderator will share the agenda with members of the Web Team. Team members can add any items they like to the agenda at the beginning of each meeting. The moderator and the Web Team cannot veto or remove items added to the agenda. +At the start of each meeting, the moderator will share the agenda with members of the Web WG. WG members can add any items they like to the agenda at the beginning of each meeting. The moderator and the Web WG cannot veto or remove items added to the agenda. ## Meeting Participation -Meeting attendance is optional but encouraged for Web Team members. Any community member or contributor is welcome to observe public meetings. +Meeting attendance is optional but encouraged for Web WG members. Any community member or contributor is welcome to observe public meetings. -Members of the Node.js Technical Steering Committee (TSC) and core collaborators are always welcome to attend and participate in public Web Team meetings, unless otherwise stated. +Members of the Node.js Technical Steering Committee (TSC) and core collaborators are always welcome to attend and participate in public Web WG meetings, unless otherwise stated. -The Web Team may invite persons or representatives from certain projects to participate in a non-voting capacity when their expertise or input would be valuable to the discussion. +The Web WG may invite persons or representatives from certain projects to participate in a non-voting capacity when their expertise or input would be valuable to the discussion. diff --git a/onboarding/README.md b/onboarding/README.md index 748fc8e..a145b8d 100644 --- a/onboarding/README.md +++ b/onboarding/README.md @@ -1,10 +1,10 @@ # Onboarding Guide -This folder outlines the steps required to onboard a new member to the @nodejs/web team and its subteams. +This folder outlines the steps required to onboard a new member to the Node.js Web Working Group (`@nodejs/web`) and its subteams. ## General Requirements -Before onboarding the **Nominee**, ensure they have read and understand [the governance of the @nodejs/web team](../GOVERNANCE.md). +Before onboarding the **Nominee**, ensure they have read and understand [the governance of the @nodejs/web WG](../GOVERNANCE.md). - [ ] If the **Nominee** is not yet part of the @nodejs GitHub organization, verify that they have two-factor authentication enabled. Membership cannot be granted without it. -- [ ] The **Nominee** should submit a pull request to this repository, adding themselves to [the MEMBERS.md file](../MEMBERS.md). This pull request should also include this onboarding checklist, along with any additional requirements specified. +- [ ] The **Nominee** should submit a pull request to this repository, adding themselves to [the members list](../README.md#members). This pull request should also include this onboarding checklist, along with any additional requirements specified.