Skip to content
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

Producing a CoC and associated documentation on process #3

Open
keywordnew opened this issue Mar 11, 2018 · 1 comment
Open

Producing a CoC and associated documentation on process #3

keywordnew opened this issue Mar 11, 2018 · 1 comment

Comments

@keywordnew
Copy link
Member

Based on discussion in #1, there is a general consensus on having a CoC, and processes around enforcement, and reporting.

To help with starting to produce documentation, these are some examples produced so far from the discussion.

Example Code of Conducts are:

Django Project
PyCascades Conf
Write the Docs
JSConf
Contributor Covenant + tool

Examples of Reporting:

Django Project

Examples of Enforcement Guides:

JS Foundation
Django Project

@Qard
Copy link
Member

Qard commented Mar 18, 2018

NodeSchool is currently using Contributor Covenant, however we haven't yet actually had any incidents come up. Given the small size of the event though, the reporting process was pretty much just "talk to me in private" and not a whole lot else was done around that. We should probably put a little more effort into it this time around. 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants