-
-
Notifications
You must be signed in to change notification settings - Fork 274
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
Added code of conduct in Readme.md #1640
Conversation
Hi, @beckermr and @kathatherine could you please review this PR and let me know if there are any required changes? Thanks! :) |
We likely want a brief summary of the CoC here. There is a short version on the numfocus website. Maybe we can add that? |
@beckermr on it! |
README.md
Outdated
|
||
Thank you for helping make this a welcoming, friendly community for all. | ||
|
||
Note: Conda-forge adheres to [NumFOCUS Code of Conduct.](https://numfocus.org/code-of-conduct) |
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.
Note: Conda-forge adheres to [NumFOCUS Code of Conduct.](https://numfocus.org/code-of-conduct) | |
We at conda-forge adhere to the [NumFOCUS Code of Conduct.](https://numfocus.org/code-of-conduct) |
very minor, but always better to phrase things as humans rather than abstract entities, so we at conda-forge adhere to the CoC, rather than "conda-forge" as an abstract entity (presumably encompassing more than the people, like the bots, etc.) adhering to it
Thank you so much for this!! I would like to encourage you to add a very brief statement about the consequence of violating our CoC. I believe there is something about that in the docs; basically, repeated violations will lead to a ban. |
@ngam I came across the Reporting guidelines i.e https://numfocus.org/code-of-conduct#reporting-guidelines Shall I add both? Or do you think the Reporting guidelines are enough? |
Please do not bump all of core on these PRs. |
ah no worries! |
Yes, please, that's a good idea! |
Added the above. Shall I make Reporting guidelines as sub-headings instead? Or is this okay? |
I think this looks good! It makes it more prominent if they have their own subheading. Maybe @beckermr has more thoughts? |
README.md
Outdated
|
||
## Enforcement: What Happens After a Report is Filed? | ||
|
||
conda-forge and/or our event staff will attempt to ensure your safety and help with any immediate needs, particularly at an in-person event. NumFOCUS will make every effort to acknowledge receipt within 24 hours (and we’ll aim for much more quickly than that). Have a look at the process of [What Happens After a Report is Filed?](https://numfocus.org/code-of-conduct#enforcement). |
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.
We cannot speak for numfocus here.
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.
Ah! My bad! Fixed it!
Added a small fix as well. Although it isn't concerned with the targeted issue. Fixed the link of dev meeting minutes |
@beckermr updated as suggested! |
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 except for those two comments.
@kathatherine will fix it. Thanks. Also,
|
@chicken-biryani You should be fine quoting NumFocus's code of conduct directly, I've learned. They actually have a template others can follow: https://github.com/numfocus/numfocus/blob/master/manual/numfocus-coc.md Your additions look good to me. |
…nto Add-Code-of-Conduct
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.
Will merge next week unless @conda-forge/core has any further comments.
This one slipped through the cracks. Let's merge! |
This issue closes #1346
PR Checklist:
src
directory, not indocs
or in the html files