Seeking comments on Code of Conduct

[chiaral]

The code of conduct draft is located here: https://github.com/pangeo-data/governance/blob/master/conduct/code_of_conduct.md

It was, similarly to the rest of the governance document so far, drafted based on on Project Jupyter's governance repo: https://github.com/jupyter/governance/blob/master/conduct/code_of_conduct.md

Similarly to the governance document (#10) I am inviting anyone to comment on this document, for the next couple of weeks.

You can comment within this issue, or open a new issue if you feel that commenting within this thread is not the appropriate place.

[chiaral]

I personally plan to suggest some PR based on the following Code of Conducts:

https://www.womenwhocode.com/codeofconduct http://www.writespeakcode.com/code-of-conduct.html http://www.pyladies.com/CodeOfConduct/ https://github.com/clef/handbook/blob/master/Clef%20Values.md

These are not GitHub projects, except for the last one, however IMHO they can be helpful in increasing our impact on defining a Code of Conduct geared towards inclusion and diversity.

[mcgibbon]

Those look like great places to take pointers for our Code of Conduct. Some things I notice right away:

• The current code of conduct is a relatively big wall of text. The bolded bullet points further down help with quickly retaining the information, but it's only after several large paragraphs. I appreciate the more concise style of all four examples you linked. There should be a very low barrier to absorbing the most important information in this document.
• Describing consequences and reporting procedures is important. Our information about consequences is also much more verbose than the examples you linked. I appreciate those communities giving themselves broad permission to take whatever action they deem appropriate in the case of harassment. While that process likely involves the same sorts of things in our enforcement manual, I feel more confident about a harassment report being followed upon to a satisfactory resolution in the terse, upfront way consequences are described in the other documents. Perhaps following up that information with a more descriptive procedural document would be appropriate, but it does not replace the need for more straightforward wording.
• The documents you linked have sections which explicitly define harassment and discrimination. This seems like a good idea.

Thank you for taking it on yourself to put together a PR taking from these documents @chiaral! I wish I had more time to commit to my own ideas on this.

[jhamman]

@chiaral - do you feel like you can take a stab at updating the code of conduct? We obviously started with the Jupyter one but we can certainly depart from that. It may help to get a side by side summary of the key points of each.

[chiaral]

Yes, I will. It might take me a few days, but I will work on it.

[kmpaul]

Just curious how this is going.

[chiaral]

Hi! I actually started working on a couple of options today. I will submit a PR later today 👍

[kmpaul]

Oooh! Great timing. :-)

[kmpaul]

I think this PR (#16) was submitted, approved, and merged. Should we close it?