Commit 52fffee 1 parent 3b1f83a commit 52fffee Copy full SHA for 52fffee
File tree 1 file changed +2
-2
lines changed
1 file changed +2
-2
lines changed Original file line number Diff line number Diff line change @@ -18,7 +18,7 @@ invalid and are superseded by the TSC Charter.
18
18
* Add them to the ` @pkgjs/node-tsc ` team.
19
19
* Invite them to the HackerOne [ Node.js team] ( https://hackerone.com/organizations/nodejs/settings/users ) .
20
20
Have them turn on two-factor authentication after they have joined.
21
- * Add them to the ` tsc ` and ` crypto-export ` mailing lists.
21
+ * Add them to the ` tsc ` mailing list: < https://github.com/nodejs/email/edit/main/iojs.org/aliases.json >
22
22
* Add them to the [ nodejs-tsc] ( https://groups.google.com/g/nodejs-tsc ) Google Group as owners, so they receive Calendar invites for TSC meetings.
23
23
* Update the ` @nodejs/node ` repository README to reflect membership in the TSC.
24
24
* Update < https://github.com/nodejs/create-node-meeting-artifacts/blob/main/templates/invited_tsc > to reflect membership in the TSC.
@@ -44,7 +44,7 @@ invalid and are superseded by the TSC Charter.
44
44
* [ ` @pkgjs ` ] ( https://github.com/orgs/pkgjs/people )
45
45
* Remove them from the HackerOne [ Node.js team] ( https://hackerone.com/organizations/nodejs/settings/users ) unless they need access for a
46
46
reason other than TSC membership.
47
- * Remove them from the ` tsc ` and ` crypto-export ` mailing lists: < https://github.com/nodejs/email/edit/main/iojs.org/aliases.json > .
47
+ * Remove them from the ` tsc ` mailing lists: < https://github.com/nodejs/email/edit/main/iojs.org/aliases.json > .
48
48
* Remove them from the [ nodejs-tsc] ( https://groups.google.com/g/nodejs-tsc ) Google Group.
49
49
* Update the ` @nodejs/node ` repository README to reflect membership in the TSC.
50
50
In all likelihood, they should be listed as TSC regular members.
You can’t perform that action at this time.
0 commit comments