Attempt to remove CommComm from README (#742)

Co-authored-by: Antoine du Hamel <[email protected]>

Author: benjamingr

README.md

@@ -1,15 +1,16 @@
-# Administration for TSC + Community Committee collaborative efforts
-This repository is formal efforts of the Node.js project that are overseen and require input from both the [TSC](https://github.com/nodejs/TSC) and [CommComm](https://github.com/nodejs/community-committee).
+# Administration Documents for Node.js
 
-Repositories that fall under the responsibility of the TSC and CommComm:
+This repository is formal efforts of the Node.js project that are overseen by the
+[TSC](https://github.com/nodejs/TSC) regarding the less technical aspects of the project.
+
+It is also used to discuss:
 
-- This repo
 - [Getting Started](https://github.com/nodejs/getting-started)
 - The private [Moderation](https://github.com/nodejs/moderation) repo (Collaborators-only access)
 
 ## Travel Fund
 
-Each member of the Node.js organization can ask for funding to travel and spread knowledge about and support the Javascript ecosystem and the Foundation.
+Each member of the Node.js organization can ask for funding to travel and spread knowledge about and support the JavaScript ecosystem and the Foundation.
 
 The management of Travel Fund for collaborators is managed by the [OpenJS
 Foundation Cross-Project-Council](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/project-resources/MEMBER_TRAVEL_FUND.md).
@@ -23,20 +24,17 @@ Foundation Summit team](https://github.com/openjs-foundation/summit).
 
 ## Governance and Current Members
 
-The Admin repo is overseen by the [TSC](https://github.com/nodejs/TSC) and [CommComm](https://github.com/nodejs/community-committee) as collaborative groups. Any action requiring consensus and voting will abide by the following process.
-
-Members of the TSC and CommComm shall operate under Lazy Consensus as a collaborative unit in the Admin repo hereby referenced as the *Admin members*. Members shall establish appropriate guidelines for implementing Lazy Consensus (e.g. expected notification and review time periods) within the development process.
-
-For all votes, the vote must pass in both TSC and CommComm or else the motion fails. If an individual happens to be in both committees, then they would end up with two votes.
+The Admin repo is overseen by the [TSC](https://github.com/nodejs/TSC). Any
+action requiring consensus and voting will abide by the TSC process for that.
 
 ### Contacts for assistance
-- [@bnb](https://github.com/bnb) - **Tierney Cyren**, CommComm Chair
-- [@joesepi](https://github.com/joesepi) - **Joe Sepi**, CommComm OpenJS Representative
+
 - [@mhdawson](https://github.com/mhdawson) - **Michael Dawson**, TSC Chair
-- [@mmarchini](https://github.com/mmarchini) - **Mary Marchini**, TSC OpenJS Representative
+- [@mcollina](https://github.com/mcollina) - **Matteo Collina**, TSC Vice Chair
 
 ### Admin members
-All active members of the TSC and CommComm.
+
+All voting members of the TSC.
 
 ## Social Team
 
@@ -46,13 +44,8 @@ The currently active members of the [Social Team](./social-team.md):
 
 ## Node.js 1Password
 
-Thanks to 1Password's [open-source program](https://github.com/1Password/1password-teams-open-source), Node.js has been comped a paid version of 1Password.
-
-### Current account owners:
-There will always be two owners of this account - the TSC and CommComm chairpeople. These owners are expected to use their access only to maintain the account and not for access to credientials that they do not otherwise explicitly have access to through [Groups](#1password-groups) within.
-
-- [@bnb](https://github.com/bnb) - **Tierney Cyren**, CommComm Chair
-- [@mhdawson](https://github.com/mhdawson) - **Michael Dawson**, TSC Chair
+Thanks to 1Password's [open-source program](https://github.com/1Password/1password-teams-open-source),
+Node.js has been comped a paid version of 1Password, managed by the TSC chair person.
 
 ### 1Password Groups