-
Notifications
You must be signed in to change notification settings - Fork 658
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
Point to new reporting form link (owned by [email protected]) #4298
Conversation
Linter Bot Results:Hi @jennaswa! Thanks for making this PR. We linted your code and found the following: There are currently no issues detected! 🎉 |
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.
lgtm
Actually @jennaswa can you tick that lgplv2 box please? |
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## develop #4298 +/- ##
===========================================
- Coverage 93.40% 93.39% -0.02%
===========================================
Files 170 184 +14
Lines 22257 23365 +1108
Branches 4071 4071
===========================================
+ Hits 20790 21822 +1032
- Misses 951 1026 +75
- Partials 516 517 +1 ☔ View full report in Codecov by Sentry. |
Done! Are you able to run the TOC command easily before merging? |
CODE_OF_CONDUCT.md
Outdated
welcome reports by | ||
emailing [*Conduct-email*][conduct-mail] or | ||
in anonymous by filling out [*this form*][conduct-form]. | ||
welcome reports by filling out [*this form*][conduct-form]. |
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.
Thinking it through, should this and the other bit about events actually link to the reporting section? That way folks can read the statement about privacy etc..?
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.
This is a good point. I've (hopefully) added links to the Reporting header in the 2 places you mentioned.
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.
Links work great, thanks!
Ah didn't see the TOC question - unfortunately not until I get to a laptop again sorry:( |
No worries - let's just wait to merge this until someone is able to update the TOC |
Add TOC of DEI
Oops, I was doing stuff quickly and updated your branch directly by accident instead of opening a new PR -- is that what you had in mind @jennaswa? |
Yep, exactly that - thanks, @lilyminium! |
As long as it was created by markdown-toc-generate-toc it should be fine? |
I did it manually, but viewing the MD file the links work? |
I assumed there was a reason there being a big "don't change manually" section? |
Sure, at the end of the day it's Markdown and if it works it works IMO. An autogenerated one would probably pick up the subheadings in reporting if you wanted to re-run it though |
If we want to just do it manually from now on that's fine, but in that case please remove the bit asking for folks not to do it manually. |
@@ -3,15 +3,15 @@ every member in the MDAnalysis community so that everyone can | |||
experience a welcoming, supportive, and productive environment that is | |||
free from harassment. | |||
|
|||
<!-- markdown-toc start - Don't edit this section. Run M-x markdown-toc-generate-toc again --> |
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 we don't have to live under the tyranical rule of emacs anymore.
Update of AUTHORS and CHANGELOG with inferred author contributions. * Removed duplicate mattwthompson in 0.20.0 changelog entry.: mattwthompson was placed twice by accident, this removes this duplication. * Addition of missing authors. An retrospective analysis of the authors found via `git shortlog -s -n --email --branches="develop"` found several commits by authors which were not present in the `AUTHORS.md` file. - Zhenbo Li: commited via PR: Started tests for gnm. #803 and Make Travis run tests on OSX. #771, - Jenna M. Swarthout via PR Update CoC according to suggestions from current CoC committee #4289 and Point to new reporting form link (owned by [email protected]) #4298, - Bradley Dice via PR Fix GSD Windows compatibility #2384 , - David Minh via PR #2668 There seemed to be no indications in the above mentioned PRs that the author did not want to be in the authors file, it looks like it was just forgotten. * Addition of missing entries from the changelog Continued cross referencing of the git shortlog output but also accounting for the changelog identified several individuals that had not been included in the changelog entries for the release they contributed under. They were added to the relevant entry of the changelog based on the merge commit date. Please note that for Tone Bengsten, we a) had no github handle (so they were assigned @tbengtsen), and b) no specific commit. Given we know that this individual was including alongside the encore merge, they were assigned to the 0.16.0 release. * Update CHANGELOG * PR #1218 * PR #1284 and #1408 * PR #4109 * based on git history * PRs #803 and #771 (author addition, changelog addition) * PR #2255 and #2221 * PR #1225 * PR #4289 and #4298 * PR #4031 * PR #4085 * PR #3635 * PR #2356 * PR #2559 * No GH handle - Encore author addition @tbengtsen * PR #4184 * PR #2614 * PR #2219 * PR #2384 * PR #2668 * Add missing entry for Jenna Thanks to @fiona-naughton for helping out with digging into this data :) Co-authored-by: Fiona Naughton <[email protected]> Co-authored-by: Oliver Beckstein <[email protected]>
The CoC Committee has changed the ownership of the reporting form to [email protected]. This PR points all relevant links to the updated form.
Changes made in this Pull Request:
PR Checklist
Developers certificate of origin
📚 Documentation preview 📚: https://mdanalysis--4298.org.readthedocs.build/en/4298/