Skip to content

docs: adopt open maintainer governance model #2383

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mcollina merged 3 commits into from
Mar 4, 2026
+119 −131
Merged

docs: adopt open maintainer governance model #2383

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c50c5ab
docs: adopt open maintainer governance model
mcollina Feb 20, 2026
9597e2b
docs: fix GOVERNANCE.md indentation for eclint
mcollina Feb 21, 2026
da3ae41
docs: align maintainers list with active collaborators
mcollina Feb 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
docs: fix GOVERNANCE.md indentation for eclint
  • Loading branch information
@mcollina
mcollina committed Feb 21, 2026
commit 9597e2bd64d287ef0c11a8ecfc3aa66f1d65ba52
2 changes: 1 addition & 1 deletion GOVERNANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ For governance, membership, major policy, or contentious technical changes:
1. Open an issue or PR describing the decision and proposed outcome.
2. Allow time for async feedback (normally at least 5 days).
Copy link
Copy Markdown
Contributor

@MikeMcC399 MikeMcC399 Feb 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps 7 days to cover 5 business days (which can depend on location) + weekend?

Copy link
Copy Markdown
Member

@sxa sxa Feb 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair - I think that would be consistent with the approach for the main node repository.

3. If no unresolved objections remain, a maintainer may merge/close with a
summary.
summary.

If a final decision cannot be made using Consensus Seeking, the issue should be
escalated to the Node.js TSC (for example by requesting `tsc-agenda`).
Copy link
Copy Markdown
Contributor

@MikeMcC399 MikeMcC399 Feb 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
escalated to the Node.js TSC (for example by requesting `tsc-agenda`).
escalated to the Node.js TSC (for example by requesting https://github.com/nodejs/docker-node/labels/tsc-agenda).

That should display the new label itself in the text

Copy link
Copy Markdown
Contributor

@MikeMcC399 MikeMcC399 Feb 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Like this: tsc-agenda

Expand Down