docs: clarify jurisdiction of the CoC Committee regarding Slack external connections #1286
Conversation
This file contains 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
|
/ptal |
thulieblack
approved these changes
Jul 4, 2024
|
Enforcing the CoC in external channels makes a lot of sense. Thanks for the clarification! |
|
/rtm |
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.
Description
Slack Connect allows other Slack Workspaces to connect some channels into other Workspaces, in this case, AsyncAPI.
An example is the #jsonschema channel in the AsyncAPI Slack Workspace.
Since there can be confusion about the jurisdiction of the CoC Committee, this PR is an attempt to clarify it.
The idea is that CoC should be enforced in those external channels as well since they are visible in AsyncAPI Slack Workspace.
cc @asyncapi/code_of_conduct @derberg