conda-forge.github.io Added code of conduct in Readme.md

This issue closes #1346

PR Checklist:

[ ] make all edits to the docs in the src directory, not in docs or in the html files
[X] note any issues closed by this PR with closing keywords
[ ] put any other relevant information below

Mar 25 '22 18:03 shloka-gupta

Hi, @beckermr and @kathatherine could you please review this PR and let me know if there are any required changes? Thanks! :)

Mar 25 '22 18:03 shloka-gupta

We likely want a brief summary of the CoC here. There is a short version on the numfocus website. Maybe we can add that?

Mar 25 '22 18:03 beckermr

@beckermr on it!

Mar 25 '22 18:03 shloka-gupta

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.

Mar 25 '22 19:03 ngam

Hi, @ngam that does make it more friendly and welcoming in nature! Thanks! :)

@ngam and @beckermr could you let me know if I could better the current PR?

Mar 25 '22 19:03 shloka-gupta

@ngam I came across the Reporting guidelines i.e https://numfocus.org/code-of-conduct#reporting-guidelines and 'Enforcement: What Happens After a Report is Filed?' i.e https://numfocus.org/code-of-conduct#enforcement

Shall I add both? Or do you think the Reporting guidelines are enough?

cc: @kathatherine @beckermr

Mar 25 '22 19:03 shloka-gupta

Please do not bump all of core on these PRs.

Mar 25 '22 19:03 beckermr

Sorry, @beckermr I didn't mean to.

I believe it is auto-mated like over here https://github.com/conda-forge/conda-forge.github.io/pull/1471 and here- https://github.com/conda-forge/conda-forge.github.io/pull/1620

Mar 25 '22 20:03 shloka-gupta

ah no worries!

Mar 25 '22 20:03 beckermr

Please do not bump all of core on these PRs.

I believe it is auto-mated like over here #1471 and here- #1620

Yes, it is automated because of this line: https://github.com/conda-forge/conda-forge.github.io/blob/5132c8d1d9e8886d9f778517b6a8350bbfe063c2/.github/CODEOWNERS#L1

Mar 25 '22 22:03 ngam

Shall I add both? Or do you think the Reporting guidelines are enough?

Yes, please, that's a good idea!

Mar 25 '22 22:03 ngam

Added the above.

Shall I make Reporting guidelines as sub-headings instead? Or is this okay?

Mar 25 '22 23:03 shloka-gupta

I think this looks good! It makes it more prominent if they have their own subheading. Maybe @beckermr has more thoughts?

Mar 26 '22 01:03 ngam

Added a small fix as well. Although it isn't concerned with the targeted issue. Fixed the link of dev meeting minutes

Mar 26 '22 13:03 shloka-gupta

@beckermr updated as suggested!

Mar 27 '22 21:03 shloka-gupta

@kathatherine will fix it. Thanks.

Also,

I am a little concerned though and may have messed up a little. I have copied and pasted the wordings of NumFocus directly into the sections since we adhere to them. Shall I modify the wordings of other sections as well or let it be?

Mar 30 '22 16:03 shloka-gupta

@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.

Apr 04 '22 15:04 kathatherine

Will merge next week unless @conda-forge/core has any further comments.

This one slipped through the cracks. Let's merge!

Jun 22 '23 12:06 ocefpaf