Proposed code of conduct and request for comments due Feb 26th#4922
Merged
Conversation
ye-luo
changed the title
Contributor
Author
|
Test this please |
Contributor
Author
|
Adopted. Thanks all. |
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
1 participant
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.
Suggestions for improvements on the following are requested. This PR will be kept open for two weeks and then either merged or an improved route taken based on the input received.
Following various internal discussions, this PR adds a code of conduct based on v2.1 of the contributor covenant https://www.contributor-covenant.org/version/2/1/code_of_conduct/ . This is very widely used but there are alternatives, see e.g. https://opensource.guide/code-of-conduct/
The intent is to establish clear expectations, standards, and enforcement guidelines rather than e.g. maintainers potentially having to rely on ad hoc approaches in the event of any problems. This is particularly important given the growing number of people who interact with the repository. The initial proposed contacts are myself ( @prckent ) and Brenda Rubenstein ( @dbrube , thank you ).
Thanks for comments.