docs: add community communication norms policy - #1721
Merged
RUKAYAT-CODER merged 2 commits intoSep 28, 2026
Merged
RUKAYAT-CODER merged 2 commits into
RUKAYAT-CODER merged 2 commits into
Conversation
Add a versioned reference for community communication, closing a gap in the governance set. Expected tone, the authoritative channel for each kind of message, and response-time expectations were undocumented and scattered across README.md and CONTRIBUTING.md. Governance/policies/COMMUNICATION_NORMS.md covers: - tone and etiquette, including review etiquette that complements the reviewer and author duties in CONTRIBUTING.md section 9 - official channels (Issues, PRs, Discussions, Telegram, private email) with guidance on choosing between them - response-time targets per channel and per kind of communication, marked explicitly as community norms rather than service-level agreements Governance/README.md indexes the Governance tree and records the change. Scope is self-contained to Governance/: two new files, no existing file modified. Contribution mechanics remain governed by CONTRIBUTING.md, which the new document defers to wherever the two overlap. Regression tests: not applicable. Documentation-only change adding two Markdown files; no TypeScript, configuration, schema, or dependency is touched. Governance/ sits outside the Jest root (jest.config.js rootDir 'src'), outside the TypeScript build (tsconfig.build.json includes src/**/*), and under the *.md exclusion in .dockerignore, so no existing test, build step, or runtime path is affected. Note: CONTRIBUTING.md section 7 asks for the issue number in parentheses at the end of the subject line. This change was requested without one, so it is omitted rather than guessed; please append it before merge.
|
@aliyuHabibu Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
|
Thank you for contributing to the project. |
Contributor
Author
|
@RUKAYAT-CODER Thank you and I will like to join the community of this project. Thank you as you consider |
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
2 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.
Add a versioned reference for community communication, closing a gap in the governance set. Expected tone, the authoritative channel for each kind of message, and response-time expectations were undocumented and scattered across README.md and CONTRIBUTING.md.
Governance/policies/COMMUNICATION_NORMS.md covers:
Governance/README.md indexes the Governance tree and records the change.
Scope is self-contained to Governance/: two new files, no existing file modified. Contribution mechanics remain governed by CONTRIBUTING.md, which the new document defers to wherever the two overlap.
Regression tests: not applicable. Documentation-only change adding two Markdown files; no TypeScript, configuration, schema, or dependency is touched. Governance/ sits outside the Jest root (jest.config.js rootDir 'src'), outside the TypeScript build (tsconfig.build.json includes src/**/*), and under the *.md exclusion in .dockerignore, so no existing test, build step, or runtime path is affected.
Note: CONTRIBUTING.md section 7 asks for the issue number in parentheses at the end of the subject line. This change was requested without one, so it is omitted rather than guessed; please append it before merge.
Closes #1597