Add Slack and GitHub etiquette guidelines to CONTRIBUTING.md #947
+32
−0
Conversation
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
This update introduces a new "Communication Etiquette" section in CONTRIBUTING.md, outlining best practices for Slack and GitHub interactions. Guidelines cover respectful communication, reducing unnecessary mentions, proper PR/issue context, and keeping discussions organized. Addresses and closes issue json-schema-org#845.
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.
Extended description:
This update introduces a new "Communication Etiquette" section in CONTRIBUTING.md, outlining best practices for Slack and GitHub interactions. Guidelines cover respectful communication, reducing unnecessary mentions, proper PR/issue context, and keeping discussions organized. Addresses and closes issue #845.
GitHub Issue:
#845
Summary:
Adds comprehensive etiquette guidelines for Slack and GitHub usage, compiling existing suggestions and open-source community best practices, to foster better communication in the JSON Schema community.
Do you think resolving this issue might require an Architectural Decision Record (ADR)?
No
Not a significant or noteworthy architectural change; this PR only adds communication guidelines as mentioned in the issue.