-
Notifications
You must be signed in to change notification settings - Fork 340
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
Adopt Contributor Covenant Code of Conduct version 2.1 #1324
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1324 +/- ##
=======================================
Coverage 97.21% 97.21%
=======================================
Files 83 83
Lines 7961 7961
=======================================
Hits 7739 7739
Misses 222 222 Continue to review full report at Codecov.
|
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.
That did not diff well at all. 😅
Looks good to me, though!
docs/CODE_OF_CONDUCT.rst
Outdated
good faith may face temporary or permanent repercussions as determined | ||
by other members of the project’s leadership. | ||
be reported to the community leaders responsible for enforcement at | ||
``[email protected]``. All complaints will be reviewed and |
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.
Does sphinx
have an email role?
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.
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.
Another possible solution...
Co-authored-by: Erik Everson <[email protected]>
Co-authored-by: Erik Everson <[email protected]>
good faith may face temporary or permanent repercussions as determined | ||
by other members of the project’s leadership. | ||
be reported to the community leaders responsible for enforcement at | ||
[email protected]. All complaints will be reviewed and |
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.
It turns out that Sphinx will render email addresses correctly with a mailto:
prefix if they show up in plain text.
Earlier this afternoon I incorporated @rocco8773's suggestions and made a few other slight changes, so this is ready for review again. I also created the conduct at plasmapy.org email group. Thanks! |
This PR is to update our code of conduct to the Contributor Covenant Code of Conduct v2.1.
Our current code of conduct is a hybrid between Astropy's and an older version of the Contributor Covenant. One of the things missing from our current code of conduct is an enforcement policy (#403). Versions 2.0 and 2.1 of the Contributor Covenant do an enforcement policy, which is a significant improvement on our current code of conduct. The Contributor Covenant is also effectively becoming the standard code of conduct for open source projects, and it was even the code of conduct that we adopted for Plasma Hack Week. The Contributor Covenant is also time-tested and community-maintained. This PR would need the approval of the Coordinating Committee, I think.
Remaining tasks...
README.md
(following instructions on the Contributor Covenant website)Closes #403. Closes #853. This follows up on #854.