-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refresh Code of Conduct from v1.4 to v2.0 #673
Conversation
1add0c1
to
81a9f8f
Compare
Looks good to me, but let's hear more from @GenericMappingTools/python @GenericMappingTools/python-contributors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great @weiji14! I quite like v2.0, in particular the enforcement guidelines. Gives the CoC a more concrete feeling.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks OK to merge.
Cool! I'll leave it open for a few more days (before v0.2.1 #665 is about to be released) in case anyone else wants to voice their opinion. |
Description of proposed changes
Refreshes our code of conduct from v1.4 to v2.0, and also add a
badge to the main README.md. Community discussion can take place at #672.
Changes (copied from https://github.com/ContributorCovenant/contributor_covenant/blob/29000ea9977e75b76189335f376a42a833972433/changelog#L19-L26):
The text is copied over from https://www.contributor-covenant.org/version/2/0/code_of_conduct/. Feel free to tweak any of the points if there is anything you feel should be in (or not in) the document.
Fixes #672
Reminders
make format
andmake check
to make sure the code follows the style guide.doc/api/index.rst
.Notes
/format
in the first line of a comment to lint the code automatically