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

doc: clarified use of sexual language in the CoC #6973

Closed
wants to merge 1 commit into from

Conversation

nebrius
Copy link
Contributor

@nebrius nebrius commented May 25, 2016

Clarifies the code of conduct by adding some wording discouraging the
use of sexualized language.

This PR was prompted by some moderation discussion, and we realized
that there was some ambiguity around this topic in the current CoC

Clarifies the code of conduct by adding some wording discouraging the
use of sexualized language.

This PR was prompted by some moderation discussion, and we realized
that there was some ambiguity around this topic in the current CoC
@nodejs-github-bot nodejs-github-bot added the meta Issues and PRs related to the general management of the project. label May 25, 2016
@scottgonzalez
Copy link
Contributor

Looks good.

@jasnell
Copy link
Member

jasnell commented May 25, 2016

LGTM

3 similar comments
@MylesBorins
Copy link
Contributor

LGTM

@addaleax
Copy link
Member

LGTM

@Qard
Copy link
Member

Qard commented May 25, 2016

LGTM

@addaleax addaleax added the doc Issues and PRs related to the documentations. label May 25, 2016
@mhdawson
Copy link
Member

LGTM

jasnell pushed a commit that referenced this pull request May 27, 2016
Clarifies the code of conduct by adding some wording discouraging the
use of sexualized language.

This PR was prompted by some moderation discussion, and we realized
that there was some ambiguity around this topic in the current CoC

PR-URL: #6973
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
@jasnell
Copy link
Member

jasnell commented May 27, 2016

Landed in d5339b3

@jasnell jasnell closed this May 27, 2016
Fishrock123 pushed a commit to Fishrock123/node that referenced this pull request May 30, 2016
Clarifies the code of conduct by adding some wording discouraging the
use of sexualized language.

This PR was prompted by some moderation discussion, and we realized
that there was some ambiguity around this topic in the current CoC

PR-URL: nodejs#6973
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
@rvagg
Copy link
Member

rvagg commented May 31, 2016

Can someone either write, or point me to a resource that provides a justification for this kind of restriction?

@nebrius
Copy link
Contributor Author

nebrius commented May 31, 2016

I don't know if there's a writeup on it...generally speaking there aren't writeups of how specific sections or clauses of CoC's are necessary. I will say though that pretty much every CoC includes language like this, including the Contributor Convenant, which is by far the most popular CoC for open source projects, and it was unusual for us not to have it.

The reason it's important is that best case scenario it's distracting, and in some cases can actively discourage people from joining. Participating in an open source project can be tough to begin with, it takes time and there are a lot of hurtles to jump through (did I write tests correctly? Is my code style correct? etc), and so we want to reduce as many barriers to entry as possible. Since this is open source, and most people are volunteering, "I'm annoyed" is a barrier to entry. Some barriers to entry are good (we want tests), but some don't serve any real purpose, and I think this falls in the latter category.

I'll give an example I relate to personally, as sexualized language doesn't bother me personally. I'm not straight, so if I come across a discussion where people are using various homophobic slurs to describe something technical (e.g. "your solution is gay"), there's a pretty good chance I won't engage because I don't like hanging around those environments. It's not that I'm offended (I very rarely get offended), but I'm annoyed. Why would I want to hang out with people who use language that has very real world history with abuse and marginalization? The answer is I don't, so I don't get involved.

@rvagg
Copy link
Member

rvagg commented Jun 2, 2016

thanks @nebrius, the response is appreciated, I'll take up further concerns in a more private forum

rvagg pushed a commit that referenced this pull request Jun 2, 2016
Clarifies the code of conduct by adding some wording discouraging the
use of sexualized language.

This PR was prompted by some moderation discussion, and we realized
that there was some ambiguity around this topic in the current CoC

PR-URL: #6973
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
MylesBorins pushed a commit that referenced this pull request Jul 11, 2016
Clarifies the code of conduct by adding some wording discouraging the
use of sexualized language.

This PR was prompted by some moderation discussion, and we realized
that there was some ambiguity around this topic in the current CoC

PR-URL: #6973
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
MylesBorins pushed a commit that referenced this pull request Jul 12, 2016
Clarifies the code of conduct by adding some wording discouraging the
use of sexualized language.

This PR was prompted by some moderation discussion, and we realized
that there was some ambiguity around this topic in the current CoC

PR-URL: #6973
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
MylesBorins pushed a commit that referenced this pull request Jul 12, 2016
Clarifies the code of conduct by adding some wording discouraging the
use of sexualized language.

This PR was prompted by some moderation discussion, and we realized
that there was some ambiguity around this topic in the current CoC

PR-URL: #6973
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Jul 12, 2016
MylesBorins pushed a commit that referenced this pull request Jul 14, 2016
Clarifies the code of conduct by adding some wording discouraging the
use of sexualized language.

This PR was prompted by some moderation discussion, and we realized
that there was some ambiguity around this topic in the current CoC

PR-URL: #6973
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
MylesBorins pushed a commit that referenced this pull request Jul 14, 2016
Clarifies the code of conduct by adding some wording discouraging the
use of sexualized language.

This PR was prompted by some moderation discussion, and we realized
that there was some ambiguity around this topic in the current CoC

PR-URL: #6973
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations. meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants