Skip to content

Commit 07153d0

Browse files
TrottTrott
authored
decharter Ecosystem Security Working Group (#1351)
* decharter Ecosystem Security Working Group It seems that the working group can function as a GitHub team. Closes: #1081 * fixup! decharter Ecosystem Security Working Group
1 parent e8e2e92 commit 07153d0

1 file changed

Lines changed: 15 additions & 38 deletions

File tree

‎WORKING_GROUPS.md‎

Lines changed: 15 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@ Working Groups can be formed at any time but must be ratified by the TSC.
77
Once formed the work defined in the Working Group charter is the
88
responsibility of the WG rather than the TSC.
99

10-
It is important that Working Groups are not formed pre-maturely. Working
11-
Groups are not formed to _begin_ a set of tasks but instead are formed
10+
It is important that Working Groups are not formed prematurely. Working
11+
Groups are not formed to begin a set of tasks but instead are formed
1212
once that work is already underway and the contributors
1313
think it would benefit from being done as an autonomous project.
1414

@@ -26,34 +26,34 @@ the working group's repository.
2626

2727
## Starting A Core Working Group
2828

29-
A Working Group is established by first defining a charter that can be
30-
ratified by the TSC. A charter is a _statement of purpose_, a
31-
_list of responsibilities_ and a _list of initial membership_.
29+
A Working Group is established by first defining a charter that can be
30+
ratified by the TSC. A charter is a statement of purpose and a
31+
list of responsibilities. When requesting that a working group be chartered, it
32+
is also necessary to provide a list of initial membership.
3233

3334
A working group needs 3 initial members. These should be individuals
3435
already undertaking the work described in the charter.
3536

3637
The list of responsibilities should be specific. Once established, these
3738
responsibilities are no longer governed by the TSC and therefore should
3839
not be broad or subjective. The only recourse the TSC has over the working
39-
group is to revoke the entire charter and take on the work previously
40-
done by the working group themselves.
40+
group is to revoke the entire charter.
4141

42-
If the responsibilities described in the charter are currently
43-
undertaken by another WG then the charter will additionally have to be
44-
ratified by that WG.
42+
If the responsibilities described in the charter are currently undertaken by
43+
another working group then the charter will additionally have to be ratified by
44+
that working group.
4545

46-
You can submit the WG charter for ratification by sending
47-
a Pull Request to this document, which adds it to the
48-
list of current Working Groups. Once ratified the list of
46+
You can submit the working group charter for ratification by sending
47+
a pull request to this document to add the charter it to the
48+
list of current Working Groups. Once ratified, the list of
4949
members should be maintained in the Working Group's
5050
README.
5151

5252
## Bootstrap Governance
5353

54-
Once the TSC ratifies a charter the WG inherits the following
54+
Once the TSC ratifies a charter, the working group inherits the following
5555
documentation for governance, contribution, conduct and an MIT
56-
LICENSE. The WG is free to change these documents through their own
56+
LICENSE. The working group is free to change these documents through their own
5757
governance process, hence the term "bootstrap."
5858

5959
```markdown
@@ -240,7 +240,6 @@ The [Node.js Code of Conduct][] applies to this WG.
240240
* [Docker](#docker)
241241
* [Addon API](#addon-api)
242242
* [Release](#release)
243-
* [Ecosystem Security](#ecosystem-security)
244243
* [Package Maintenance](#package-maintenance)
245244
* [Undici](#undici)
246245

@@ -403,27 +402,6 @@ Responsibilities include:
403402
backporting changes to these branches.
404403
* Define the policy for what gets backported to release streams.
405404

406-
### [Security](https://github.com/nodejs/security-wg)
407-
408-
The Security Working Group works to improve the security of Node.js and its ecosystem.
409-
410-
Responsibilities include:
411-
412-
* Ensure the vulnerability data is updated in an efficient and timely manner. For example, ensuring there
413-
are well-documented processes for reporting vulnerabilities in community
414-
modules.
415-
* Maintain and make available data on disclosed security vulnerabilities in:
416-
* the core Node.js project
417-
* other projects maintained by the overall Node.js project
418-
* the external Node.js open source ecosystem
419-
* Promote the improvement of security practices within the Node.js ecosystem.
420-
* Facilitate and promote the expansion of a healthy security service and product
421-
provider ecosystem.
422-
423-
This Working Group is _not_ responsible for managing or responding to
424-
security reports against Node.js itself. That responsibility remains with
425-
the [Node.js TSC][].
426-
427405
### [Package Maintenance](https://github.com/nodejs/package-maintenance)
428406

429407
Responsibilities include:
@@ -458,5 +436,4 @@ Responsibilities include:
458436
* Documenting the undici API, examples, and best practices.
459437
* Development of Node.js HTTP Client APIs such as a WHATWG Fetch implementation.
460438

461-
[Node.js TSC]: https://github.com/nodejs/tsc
462439
[Technical Steering Committee (TSC)]: ./TSC-Charter.md

0 commit comments

Comments
 (0)