doc: update Code of Conduct to Contributor Covenant 3.0 - #1097
Open
bmuenzenmeyer wants to merge 3 commits into
Open
bmuenzenmeyer wants to merge 3 commits into
bmuenzenmeyer wants to merge 3 commits into
Conversation
Contributor
Author
|
This is a "byte-identical" framing of Contributor Covenant 3 with placeholders addressed with our own policies or teams, but I plan to review that in earnest and report it here. |
Open
4 of 6 tasks
Contributor Covenant 3.0 restricts "sharing or acting on someone's
personal or private information without their permission", but does not
say how that interacts with reporting an incident. Read narrowly, it
leaves a reporter unsure whether forwarding a harassing direct message to
report@nodejs.org is itself a violation.
v3.0 also drops two v2.0 clauses that covered private conduct:
* "Public or private harassment"
* "Other conduct which could reasonably be considered inappropriate in
a professional setting"
v3.0's harassment restriction requires an explicitly expressed boundary
or a prior request to stop, so publishing a private communication in
order to win a public argument is no longer clearly covered by anything
other than the catch-all.
This adds a Node.js-specific Confidentiality section that:
* exempts information shared with the Moderation Team when reporting or
investigating, so forwarding a private message to report@nodejs.org
is never itself a violation
* reads "personal or private information" to include statements made in
a private setting, not only identifying details
* distinguishes describing someone's conduct toward you, which is not a
disclosure, from republishing their private words to apply pressure
or to enlist their view, which is
Upstream v3.0 text is left byte-identical so future updates stay easy to
diff. Kept as a separate commit so it can be dropped independently of the
Contributor Covenant 3.0 upgrade.
bmuenzenmeyer
commented
Sep 6, 2026
bmuenzenmeyer
left a comment
bmuenzenmeyer
left a comment
Contributor
Author
There was a problem hiding this comment.
self-review with explicit call outs
| When an incident does occur, it is important to report it promptly. To report a possible violation, contact the [Node.js Moderation Team][] at [report@nodejs.org][]. Additional ways to request moderation, including opening an issue in a Node.js repository, are described in the [Moderation Policy][]. | ||
|
|
||
| ### 2. Warning | ||
| The [Node.js Moderation Team][] takes reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. The Moderation Team will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution. |
Contributor
Author
There was a problem hiding this comment.
this supports scoping questions made within openjs-foundation/cross-project-council#1701 (comment)
| ### Other Restrictions | ||
|
|
||
| Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: | ||
| 1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions. |
Contributor
Author
There was a problem hiding this comment.
new - alt accounts and evasion is explicitly banned
| ## Reporting an Issue | ||
|
|
||
| **Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. | ||
| Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm. |
Contributor
Author
There was a problem hiding this comment.
"Not every conflict represents a code of conduct violation" hopefully this is a welcome addition.
| professional setting | ||
| While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language. | ||
|
|
||
| ## Enforcement Responsibilities |
Contributor
Author
There was a problem hiding this comment.
this is now mostly in the moderation policy instead of repeated
jasnell
approved these changes
Sep 6, 2026
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
4 participants
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.
Note
This proposal has a bit more ambiguity than the others, and should be considered later in the session.
Upgrades the Node.js Code of Conduct to Contributor Covenant v3.
Looking for a diff? There isn't really one, but I will do my best to call out important new clauses for discussion and alignment.
Refs:
Assisted by: Claude Opus