Removing the CoC copy in favor of the org-level template #4200
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
At some point we set an org-level CoC, so to this refers to that centralized document in order to maintain a single instance.
|
My vague recollection is that we added the CoC to get a green check for this in the "Community Standards" page on GitHub: 
Will will lose the green check if we remove this file? If so, do we care? |
Let's find out 😎 |
ralfhandl
approved these changes
Nov 14, 2024
lornajane
approved these changes
Nov 14, 2024
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.
IIUC, the org level CoC will be used if no file exists at the repo level. Unless there is some clear reason why we want to keep separate documents in sync, I think we should remove it. Then, like Arazzo, it should pick up the CoC on the landing page as well as the various appropriate areas like issue filing.
... and if there are clear reasons why we don't want to remove this copy, then please close this PR without merging.