Code of Conduct / Statement of Diversity and Inclusion

[germonprez]

I believe that we should be explicit on these in the repository.

[aserebrenik]

We can consider adopting the Contributor Covenant (https://www.contributor-covenant.org/) or propose something ourselves.

[germonprez]

@aserebrenik -- Thanks for sharing this. @GeorgLink, are you leading the CoC? Would the contributor covenant be helpful?

[jgbarah]

I would rather prefer something more simple, such as what they did for OPNFV,

https://wiki.opnfv.org/display/DEV/OPNFV+Community+Code+of+Conduct

[rpaik]

You can also check out code of conducts from other open source communities (e.g. Ubuntu[1], OpenStack[2], Hyperledger[3] etc.). Many of the good ones are fairly concise (esp. on the main points they want to strive towards).

I think being concise is especially important if we want to be inclusive of people from different countries where English is not their native language. Short/bullet points (~10 items) usually work better...

[1] https://www.ubuntu.com/about/about-ubuntu/conduct
[2] https://www.openstack.org/legal/community-code-of-conduct/
[3] https://wiki.hyperledger.org/community/hyperledger-project-code-of-conduct

[ghost]

Safety First PDX has done a lot of research on Codes of Conduct, particularly around FOSS projects. Here's some of their recommendations: http://safetyfirstpdx.org/training/code_of_conduct/code_of_conduct.html

Specific recommendation relevant here:

A list of specific behaviors considered inappropriate - These need to cover common types of harassment and abuse. Specifics are important because they reduce the ambiguity of these requests: it’s easier to understand and follow ‘when someone says they don’t want to talk to you, stop’ versus ‘don’t be a jerk’.

[germonprez]

Thanks everyone!

[GeorgLink]

Thanks everyone. I'll send an email to form a working group and move this forward.

[germonprez]

Can we close this issue and open a new one as needed for the CoC?

[GeorgLink]

I was leaving this open for when we do have the CoC, which should be soon. We are making good progress on the CoC working group. If you prefer to close this, that's fine too.

[germonprez]

I'm fine either way. Not a big deal :)

…

On Thu, Nov 30, 2017 at 3:43 PM, Georg J.P. Link ***@***.***> wrote: I was leaving this open for when we do have the CoC, which should be soon. We are making good progress on the CoC working group. If you prefer to close this, that's fine too. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#26 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAoDUIeby_vnpr4nD7qqkeUe9yMEvwtzks5s7yGfgaJpZM4Ppi_E> .

-- Mutual of Omaha Associate Professor Information Systems College of Information Science & Technology University of Nebraska Omaha https://goo.gl/E87KdK