doc: adds Charter

.github/CODEOWNERS

@@ -1,2 +1 @@
 * @nodejs/web-admins
-GOVERNANCE.md @nodejs/tsc

.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"],

CHARTER.md

@@ -0,0 +1,40 @@
+# Web Working Group 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](https://github.com/nodejs/web-team/blob/main/PERMISSIONS.md).
+* Responding to availability and security incidents affecting the Node.js web
+  presence, per the Working Group's
+  [incident response plan](https://github.com/nodejs/web-team/blob/main/INCIDENT_RESPONSE_PLAN.md).
+* Maintaining localization tooling and workflows for the Node.js website.
+* Project governance and process for the Working Group, including its own
+  governance, contribution, and permissions policies.
+* Managing the membership of `@nodejs/web` and its subteams, including
+  `@nodejs/nodejs-website`, `@nodejs/doc-kit`, `@nodejs/web-infra`, and `@nodejs/web-admins`.
+* Overseeing repositories within the Working Group's scope (
+  archiving, removing) and their maintainer teams.
+
+The following remain outside the charter:
+
+* Website changes expressing a position about a global event or group of people,
+  which continue to require TSC approval.
+* Website content governed by the
+  [content vs. code](https://github.com/nodejs/nodejs.org/blob/main/docs/content-vs-code.md)
+  guidance, including OpenJS Foundation requests.
+* Cloudflare, which is owned by the Build Working Group; the Web Working Group
+  holds scoped access only.
+
+For the current list of WG members, see the
+[README](https://github.com/nodejs/web-team/blob/main/README.md#members).

README.md

@@ -1,15 +1,94 @@
-# 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. What
+it is responsible for, and what remains outside its scope, is defined in the
+[Charter](CHARTER.md). How it operates is defined in
+[GOVERNANCE.md](GOVERNANCE.md).
+
+For the current list of WG members, see [Members](#members).
+
+## Working Group Structure
+
+The Working Group ([`@nodejs/web`](https://github.com/orgs/nodejs/teams/web))
+consists of four specialized subteams:
 
 - **Website Team** ([`@nodejs/nodejs-website`](https://github.com/orgs/nodejs/teams/nodejs-website)) - Day-to-day website development
+- **Doc Kit Team** ([`@nodejs/doc-kit`](https://github.com/orgs/nodejs/teams/doc-kit)) - Day-to-day development of [nodejs/doc-kit](https://github.com/nodejs/doc-kit)
 - **Web Infra Team** ([`@nodejs/web-infra`](https://github.com/orgs/nodejs/teams/web-infra)) - Infrastructure and CI/CD
+- **Web Admins Team** ([`@nodejs/web-admins`](https://github.com/orgs/nodejs/teams/web-admins)) - Administrative operations relating to the Working Group
+
+For detailed information about each team's responsibilities, see
+[GOVERNANCE.md](GOVERNANCE.md).
+
+## Governance
+
+The Working Group's scope is defined in the [Charter](CHARTER.md). The policies
+it operates under live in [GOVERNANCE.md](GOVERNANCE.md):
+
+- [TSC Oversight](GOVERNANCE.md#tsc-oversight) and
+  [OpenJS Oversight and Content Input](GOVERNANCE.md#openjs-oversight-and-content-input)
+- [Collaborators](GOVERNANCE.md#collaborators) and
+  [Pull Request Policies](GOVERNANCE.md#pull-request-policies)
+- [WG Membership](GOVERNANCE.md#wg-membership) and
+  [Special Access Requests](GOVERNANCE.md#special-access-requests)
+- [WG Meetings](GOVERNANCE.md#wg-meetings) and
+  [Consensus Seeking Process](GOVERNANCE.md#consensus-seeking-process)
+- [Moderation Policy](GOVERNANCE.md#moderation-policy) and
+  [Code of Conduct](GOVERNANCE.md#code-of-conduct)
+
+## 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** <<me@aviv.sh>> (he/him)
+- [@bmuenzenmeyer](https://github.com/bmuenzenmeyer) - **Brian Muenzenmeyer** <<brian.muenzenmeyer@gmail.com>> (he/him)
+- [@canerakdas](https://github.com/canerakdas) - **Caner Akdas** <<canerakdas@gmail.com>> (he/him)
+- [@flakey5](https://github.com/flakey5) - **flakey5** <<me@flakey5.dev>> (she/her)
+- [@MattIPv4](https://github.com/MattIPv4) - **Matt Cowley** <<me@mattcowley.co.uk>> (he/him)
+- [@MoLow](https://github.com/MoLow) - **Moshe Atlow** <<moshe@atlow.co.il>> (he/him)
+- [@ovflowd](https://github.com/ovflowd) - **Claudio Wunder** <<cwunder@gnome.org>> (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)
+
+## In This Repository
 
-_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._
+| Document                                               | Contents                                                                    |
+| ------------------------------------------------------ | --------------------------------------------------------------------------- |
+| [CHARTER.md](CHARTER.md)                               | What the Working Group is, and is not, responsible for                      |
+| [GOVERNANCE.md](GOVERNANCE.md)                         | Subteam responsibilities, membership, meetings, and decision making         |
+| [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).
+[Node.js Core Working Group]: https://github.com/nodejs/TSC/blob/main/WORKING_GROUPS.md
+[Technical Steering Committee (TSC)]: https://github.com/nodejs/TSC/blob/main/TSC-Charter.md

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)**
 

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.

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 @nodejs/web WG 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.