Skip to content

doc: move Code of Conduct and Moderation Policy to admin repo #395

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

Merged
merged 3 commits into from
Nov 23, 2017

Conversation

MylesBorins
Copy link
Contributor

This will require nodejs/admin#25 to land
first

@MylesBorins MylesBorins changed the title doc: move Code of Conduct to admin repo doc: move Code of Conduct and Moderation Policy to admin repo Oct 23, 2017
@MylesBorins
Copy link
Contributor Author

I've updated this to move both the CoC and Moderation Policy

@MylesBorins
Copy link
Contributor Author

I've also updated the base policies that are copied when creating new working groups

@jasnell
Copy link
Member

jasnell commented Oct 24, 2017

I think I'm generally -1 on moving the CoC. I think there is value in having the CoC here and there's no harm in the CommComm having it's own copy or even it's own text.

I'm good with moving the Moderation policy.

@MylesBorins
Copy link
Contributor Author

@jasnell can you expand on the specific value of the TSC having it's own CoC? It seems odd that the CoC would live in this repo and the guidelines in another, pretty counter intuitive.

The CommComm will need a CoC as well, and I think it is a good thing, at least for the beginning, that we coalesce.

@jasnell
Copy link
Member

jasnell commented Oct 24, 2017

can you expand on the specific value ...

Every time we move this document back a layer, we essentially add a new layer of abstraction. Having the TSC own the CoC for the technical project makes the TSC more directly responsible for ensuring it's enforcement within the project. Yes, there are some logistical processes and activities that we can share effectively with CommComm (like the day to day management of the github org, moderation activities, etc), but the idea of the TSC actively managing the technical project and actively enforcing it's own policies is something that cannot be outsourced or shared.

Yes, it would be a good thing for the CommComm to have a CoC, and ideally that would use the same text as the TSC CoC, but they don't have to live in the same spot.

@mhdawson
Copy link
Member

I don't think we need separate copies unless they are different.

Could just just have a line in the README.md for the TSC that states the CoC is the version in the admin repo. If at some point the TSC one needs to diverge the different copy could be in the TSC repo and the reference could be changed. I don't think having a duplicate copy is going to change the level of ownership.

@MylesBorins
Copy link
Contributor Author

@mhdawson that was my thought as well. Unless we explicitly need to diverge I think having separate copies only increases the odds of divergence. Further, if both TSC + commcomm are using the the same CoC, it doesn't really make sense to have it anywhere but admin

@MylesBorins
Copy link
Contributor Author

I've updated the copy on the code of conduct
@jasnell can you ptal?

Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, looks ready to land.

@MylesBorins MylesBorins merged commit 64f9cf8 into nodejs:master Nov 23, 2017
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

Successfully merging this pull request may close these issues.

4 participants