doc: Charter the package-maintenance working group #880
Conversation
Refs: nodejs/admin#470 Refs: nodejs/package-maintenance#338 Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com>
|
@nodejs/commit-queue FYI since its related to a new org that was requested in the admin repo. |
|
Out of curiosity, what is the necessity of chartering the pkg maintenance group? This would bring some clarity on why it makes sense for some groups but perhaps not for others (I hope). |
@mhdawson Did you intend to tag CommComm here, perhaps? |
|
FYI @nodejs/community-committee. @Trott thanks for catching that. |
|
@boneskull, in this case the specific reason to charter was so that authority for the management of the pkgjs repo could be delegated to that working group. |
@mdawson I assume you mean the org. Is there something in the bylaws that requires this? Or rather, does it make the |
It will become an official org owned by the Node.js Project, moderated by the moderation team etc. |
|
@nodejs/tsc this has been opened for 3 weeks and has 2 approvals. Unless there are objections in the TSC meeting today we'll assume there is consensus and land. |
|
No objections in today's meeting, landing. |
Refs: nodejs/admin#470
Refs: nodejs/package-maintenance#338
Signed-off-by: Michael Dawson michael_dawson@ca.ibm.com
470 includes the initial request for a separate org under the auspices of the Node.js project and the agreement for that.
338 includes the governance updates which document who the new org will be managed by the package-maintenance WG.