Repository navigation
doc: document the @nodejs/doc-kit subteam - #176
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 <[email protected]>
MattIPv4
approved these changes
Aug 29, 2026
avivkeller
suggested changes
Aug 29, 2026
avivkeller
reviewed
Aug 29, 2026
Co-authored-by: Copilot Autofix powered by AI <[email protected]> Co-authored-by: Aviv Keller <[email protected]>
Clarified the scope and access rights of the Node.js Doc Kit Team.
bjohansebas
approved these changes
Aug 30, 2026
bmuenzenmeyer
requested changes
Sep 30, 2026
avivkeller
reviewed
Sep 30, 2026
avivkeller
reviewed
Sep 30, 2026
avivkeller
reviewed
Sep 30, 2026
avivkeller
reviewed
Sep 30, 2026
avivkeller
reviewed
Sep 30, 2026
avivkeller
reviewed
Sep 30, 2026
Co-authored-by: Aviv Keller <[email protected]>
Assisted-by: Claude Opus 5.5 <[email protected]>
bmuenzenmeyer
approved these changes
Oct 26, 2026
bmuenzenmeyer
left a comment
bmuenzenmeyer
left a comment
Contributor
There was a problem hiding this comment.
with Write - this is a 👍 to me
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We created the @nodejs/doc-kit team on GitHub so contributors to nodejs/doc-kit can be onboarded without handing them the whole Web Team surface, and the docs here never caught up. This PR documents it:
PERMISSIONS.md: new@nodejs/doc-kitcolumn. The only non-empty cell isWriteon nodejs/doc-kit, everything else, including every external service, is-GOVERNANCE.md: new section covering the team, its scope, and its nomination process, which mirrors @nodejs/web-infraMEMBERS.md: new section, seeded with the current members of the GitHub teamonboarding/doc-kit.md: onboarding checklist, deliberately much shorter than web-infra'sREADME.md: two subteams becomes threeThe scope is intentionally narrow:
Writeon nodejs/doc-kit and nothing else. No publishing access for now, so no 1Password vault, no Vercel, no npm scope ownership, those stay with @nodejs/web-infra. Releases still go out through the repo's automated workflow via npm trusted publishing, so this doesn't block anyone from cutting one.Heads up that touching
GOVERNANCE.mdpulls in @nodejs/tsc via CODEOWNERS. Happy to split that file into its own PR if y'all would rather land the rest first.Refs: nodejs/admin#1091