Skip to content

meta: move code of conduct to it's own file - #3722

Closed
MylesBorins wants to merge 1 commit into
nodejs:masterfrom
MylesBorins:code-of-conduct
Closed

meta: move code of conduct to it's own file#3722
MylesBorins wants to merge 1 commit into
nodejs:masterfrom
MylesBorins:code-of-conduct

Conversation

@MylesBorins

Copy link
Copy Markdown
Contributor

Currently the code of conduct exists but it is somewhat hidden in
CONTRIBUTING.md

This PR creates CODE_OF_CONDUCT.md that contains the copy originally
found in CONTRIBUTING.md

Currently the code of conduct exists but it is somewhat hidden in
CONTRIBUTING.md
This PR creates CODE_OF_CONDUCT.md that contains the copy originally
found in CONTRIBUTING.md
@MylesBorins

Copy link
Copy Markdown
ContributorAuthor

@mikeal

Copy link
Copy Markdown
Contributor

habitual comment about adding more ALLCAPS top-level files

Just getting that out of the way :)

But in seriousness, it should be in CONTRIBUTING.md because only CONTRIBUTING.md is linked to when submitting a pull request.

@MylesBorins

Copy link
Copy Markdown
ContributorAuthor

That's reasonable... maybe we should add something to the README.md instead? My main concern is that the Code of conduct is not very discoverable

@mikeal

Copy link
Copy Markdown
Contributor

A link in the README seems appropriate. While we're at it we should link to all the other files there like the COLLABORATOR_GUIDE.

@MylesBorins

Copy link
Copy Markdown
ContributorAuthor

It seems like there are already a handful of links here

--> https://github.com/nodejs/node#resources-for-newcomers

I'm going to take a pass at that copy

@mscdexmscdex added the doc Issues and PRs related to the documentations. label Nov 9, 2015
@bnoordhuis

Copy link
Copy Markdown
Member

But in seriousness, it should be in CONTRIBUTING.md because only CONTRIBUTING.md is linked to when submitting a pull request.

One criticism I've heard is that no one reads it because it's too big.

@silverwind

Copy link
Copy Markdown
Contributor

How about putting it on either the Wiki or in doc? Not too fond of adding another root level file.

@MylesBorins

Copy link
Copy Markdown
ContributorAuthor

closing in lieu of #3774

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docIssues and PRs related to the documentations.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@MylesBorins@mikeal@bnoordhuis@silverwind@mscdex