Skip to content

Commit debd6c9

Browse files
committed
doc: remove explicit Charter.md
1 parent 55dcd01 commit debd6c9

3 files changed

Lines changed: 53 additions & 60 deletions

File tree

‎CHARTER.md‎

Lines changed: 0 additions & 40 deletions
This file was deleted.

‎GOVERNANCE.md‎

Lines changed: 47 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ The Node.js Web Working Group ([`@nodejs/web`](https://github.com/orgs/nodejs/te
66
is a [Node.js Core Working Group][], chartered by the
77
[Technical Steering Committee (TSC)][]. The WG is responsible for high-level
88
guidance of the Node.js web presence and has final authority over the work
9-
described in the [Charter][], and over the following teams:
9+
described in the [Charter][] below, and over the following teams:
1010

1111
- [`@nodejs/web`](https://github.com/orgs/nodejs/teams/web)
1212
- [`@nodejs/nodejs-website`](https://github.com/orgs/nodejs/teams/nodejs-website)
@@ -19,17 +19,48 @@ README.
1919

2020
## Charter
2121

22-
The Working Group's scope, both the work it is responsible for and the work that
23-
remains outside it, is defined in the [Charter][]. The Charter is the
24-
authoritative statement of that scope and is reproduced in the TSC's
25-
[WORKING_GROUPS.md][], so it is not restated here.
26-
27-
Work that the Charter does not place with the WG remains with the TSC or other WGs.
28-
Within the charter, the TSC's only recourse over a Working Group is to revoke its charter.
29-
30-
The Charter defers to two oversight clauses, described below. Chartering does not
31-
change either of them. Changes to the Cloudflare boundary the Charter describes
32-
require agreement from the [Build WG][].
22+
The Working Group is responsible for the Node.js project's web presence: the
23+
development, operation, and security of nodejs.org and the infrastructure that
24+
serves it. This section is the authoritative statement of that scope, and is
25+
reproduced in the TSC's [WORKING_GROUPS.md][].
26+
27+
Responsibilities include, except where limited by the exclusions below:
28+
29+
* Technical direction and day-to-day development of the Node.js website and its
30+
supporting projects, including `nodejs/nodejs.org`, `nodejs/learn`, and
31+
`nodejs/doc-kit`.
32+
* Operating and maintaining the infrastructure serving the Node.js web presence,
33+
including CI/CD pipelines, `nodejs/website-cloudflare-worker`,
34+
`nodejs/release-cloudflare-worker`, and `nodejs/discord-status-worker`.
35+
* Managing access to, and administration of, the third-party services used to run
36+
the Node.js web presence, as enumerated in [PERMISSIONS.md](PERMISSIONS.md).
37+
* Responding to availability and security incidents affecting the Node.js web
38+
presence, per the Working Group's
39+
[incident response plan](INCIDENT_RESPONSE_PLAN.md).
40+
* Maintaining localization tooling and workflows for the Node.js website.
41+
* Project governance and process for the Working Group, including its own
42+
governance, contribution, and permissions policies.
43+
* Managing the membership of `@nodejs/web` and its subteams, per
44+
[WG Membership](#wg-membership).
45+
* Overseeing repositories within the Working Group's scope (archiving, removing)
46+
and their maintainer teams.
47+
48+
The following remain outside the charter:
49+
50+
* Website changes expressing a position about a global event or group of people,
51+
which continue to require TSC approval, per [TSC Oversight](#tsc-oversight)
52+
below.
53+
* Website content governed by the [content vs. code][] guidance, including
54+
OpenJS Foundation requests, per
55+
[OpenJS Oversight and Content Input](#openjs-oversight-and-content-input)
56+
below.
57+
* Cloudflare, which is owned by the [Build WG][]; the Web Working Group holds
58+
scoped access only. Changing that boundary requires agreement from the
59+
Build WG.
60+
61+
Work that this charter does not place with the WG remains with the TSC or other
62+
WGs. Within the charter, the TSC's only recourse over a Working Group is to
63+
revoke its charter. Chartering does not change the two oversight clauses below.
3364

3465
### TSC Oversight
3566

@@ -42,6 +73,8 @@ or by sending an email to `tsc@iojs.org` and receive at least one approval and n
4273

4374
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][] guidance. Additionally, OpenJS Foundation requests are always honored, such as including project and foundation links in the footer.
4475

76+
## Teams
77+
4578
### Node.js Website Team (`@nodejs/nodejs-website`)
4679

4780
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.
@@ -62,7 +95,7 @@ Web Infra Team members should have access to maintain the services mentioned abo
6295

6396
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](#wg-membership).
6497

65-
\* 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). See the [Charter][] for that boundary.
98+
\* 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). See the [Charter][] above for that boundary.
6699

67100
When considering new members, approvers are primarily concerned with **competence** and **trust**. The [language within the Build WG pertaining to competence and trust][build-membership] applies here. The following is repeated, for emphasis:
68101

@@ -299,7 +332,7 @@ The [Node.js Moderation Policy][] applies to this WG.
299332
The [Node.js Code of Conduct][] applies to this WG.
300333

301334
[Build WG]: https://github.com/nodejs/build
302-
[Charter]: ./CHARTER.md
335+
[Charter]: #charter
303336
[Consensus Seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
304337
[Contributing Guidelines]: https://github.com/nodejs/nodejs.org/blob/main/CONTRIBUTING.md#becoming-a-collaborator
305338
[Approval Process]: https://github.com/nodejs/nodejs.org/blob/main/docs/collaborator-guide.md#approval-process

‎README.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,12 +4,12 @@ The Node.js Web Working Group ([`@nodejs/web`](https://github.com/orgs/nodejs/te
44
is a [Node.js Core Working Group][], chartered by the
55
[Technical Steering Committee (TSC)][].
66

7-
This repository contains the charter, governance documentation, workflows, and
7+
This repository contains the governance documentation, workflows, and
88
shared resources for the Working Group and its subteams.
99

1010
The WG is responsible for high-level guidance of the Node.js web presence. What
1111
it is responsible for, and what remains outside its scope, is defined in the
12-
[Charter](CHARTER.md). How it operates is defined in
12+
[Charter](GOVERNANCE.md#charter). How it operates is defined in the rest of
1313
[GOVERNANCE.md](GOVERNANCE.md).
1414

1515
For the current list of WG members, see [Members](#members).
@@ -29,9 +29,10 @@ For detailed information about each team's responsibilities, see
2929

3030
## Governance
3131

32-
The Working Group's scope is defined in the [Charter](CHARTER.md). The policies
33-
it operates under live in [GOVERNANCE.md](GOVERNANCE.md):
32+
The Working Group's scope and the policies it operates under both live in
33+
[GOVERNANCE.md](GOVERNANCE.md):
3434

35+
- [Charter](GOVERNANCE.md#charter), the scope of the WG
3536
- [TSC Oversight](GOVERNANCE.md#tsc-oversight) and
3637
[OpenJS Oversight and Content Input](GOVERNANCE.md#openjs-oversight-and-content-input)
3738
- [Collaborators](GOVERNANCE.md#collaborators) and
@@ -82,8 +83,7 @@ it operates under live in [GOVERNANCE.md](GOVERNANCE.md):
8283

8384
| Document | Contents |
8485
| ------------------------------------------------------ | --------------------------------------------------------------------------- |
85-
| [CHARTER.md](CHARTER.md) | What the Working Group is, and is not, responsible for |
86-
| [GOVERNANCE.md](GOVERNANCE.md) | Subteam responsibilities, membership, meetings, and decision making |
86+
| [GOVERNANCE.md](GOVERNANCE.md) | Charter, subteam responsibilities, membership, meetings, and decision making |
8787
| [PERMISSIONS.md](PERMISSIONS.md) | Repository, service, and token access held by each team |
8888
| [SECURITY.md](SECURITY.md) | How to report a security issue |
8989
| [INCIDENT_RESPONSE_PLAN.md](INCIDENT_RESPONSE_PLAN.md) | Incident classification, response, and postmortem process |

0 commit comments

Comments
 (0)