add a code of conduct

[ashleygwilliams]

this is npm's coc with some minor changes.
the node code of conduct is not complete enough.
i would like to enforce a more specific and actionable one here.
if node is interested in upstreaming this, that would be wonderful.

would love help cleaning out the npm specific content.
also we need an email address for abuse reports.

if you find mistakes please feel free to submit a PR to this branch! let me know if you need help with that at all.

[Trott]

Copy/paste error?

[ashleygwilliams]

lol yup. i knew i'd miss a bunch on the first pass. thanks!

[bnoordhuis]

I don't like the repeated use of "the Node.js community" in this document. Community covers a lot more than what's under https://github.com/nodejs.

[ashleygwilliams]

@bnoordhuis do you have a suggestion on what you'd like to replace it with? thanks!

[bnoordhuis]

Personally, I'd just drop it. If you want to have something there, what about "other Working Groups"?

[mikeal]

RE: use of Node.js Commmunity.

I see only two references to "Node.js community" and each is used quite differently.

This first is regarding banning/expulsion from the "Node.js Community." I don't know entirely what that means but I would guess that it means repos, orgs, IRC, and related community events. We could spell those all out but note that moderation above the WG would have to be escalated. While this moderation falls outside just the WG it is accurate in that if someone were to post in this repo similar anti-semitic images like we saw yesterday in the TSC repo they would be banned from all community related spaces (if they could be identified and aren't using a throwaway account).

The second reference is "Node.js community venues, online and in person" in regard to being held accountable in this repo/WG for conduct outside this repo/WG (like a conference or twitter). Basically, if someone is a known harasser in another space they won't be allowed to participate in this one. For this reference we could probably just remove "Node.js community" and reference "all venues online and in-person" as I don't think we would exclude serious conduct violations that weren't explicitly Node.js venues.

[bnoordhuis]

To clarify, when I read the word "community", I think of more than just this project. Express, hapi, my local user group, those are all part of the wider community, and outside our remit.

[jasnell]

The "I don't know entirely what that means" is the challenge,
unfortunately.
On Nov 15, 2015 1:53 PM, "Mikeal Rogers" notifications@github.com wrote:

RE: use of Node.js Commmunity.

I see only two references to "Node.js community" and each is used quite
differently.

This first is regarding banning/expulsion from the "Node.js Community." I
don't know entirely what that means but I would guess that it means repos,
orgs, IRC, and related community events. We could spell those all out but
note that moderation above the WG would have to be escalated. While this
moderation falls outside just the WG it is accurate in that if someone
were to post in this repo similar anti-semitic images like we saw yesterday
in the TSC repo they would be banned from all community related spaces (if
they could be identified and aren't using a throwaway account).

The second reference is "Node.js community venues, online and in person"
in regard to being held accountable in this repo/WG for conduct outside
this repo/WG (like a conference or twitter). Basically, if someone is a
known harasser in another space they won't be allowed to participate in
this one. For this reference we could probably just remove "Node.js
community" and reference "all venues online and in-person" as I don't think
we would exclude serious conduct violations that weren't explicitly
Node.js venues.

—
Reply to this email directly or view it on GitHub
#22 (comment).

[scottgonzalez]

double space before the last word

[scottgonzalez]

Just marking this line to make sure the contact info is filled in later.

[ashleygwilliams]

@bnoordhuis @jasnell @mikeal i believe all references to the Node.js community have been removed except for one place where it refers specfically to Node.js community members particupating in this working group (actually a direct contribution of wording from @jasnell).

is this better? thoughts on the current draft now that i've addressed all the comments?

[ashleygwilliams]

ok waiting on nodejs/email#9 and then merging

[beaugunderson]

@ashleygwilliams read through all of the discussion and I think everything has been addressed 👍 ✨

[nebrius]

LGTM, just one last question. Did we actually get the email inclusivity@nodejs.com? I think we only got inclusivity@iojs.org: nodejs/email@ea9a396

[ashleygwilliams]

the issue made it seem like they had contacted the people and got it working. lemme check my email. i got a test message.

[beaugunderson]

I do recall that the @nodejs.org alias was added as well. :)

From rvagg in the email thread:

alias was added to @nodejs.org and a test email was sent, hopefully y'all got that and can confirm it's working.

[nebrius]

LGTM! I'll leave to @beaugunderson to +1 and merge.

[beaugunderson]

👍!