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: add Inclusivity Working Group #4355

Closed
wants to merge 1 commit into from

Conversation

ashleygwilliams
Copy link
Contributor

@zkat
Copy link
Contributor

zkat commented Dec 19, 2015

LGTM although I'm not sure if mine counts for this since I'm not TSC :) 🐑

@ghost
Copy link

ghost commented Dec 19, 2015

pseudo-LGTM, also cc @nodejs/inclusivity

@mscdex mscdex added the doc Issues and PRs related to the documentations. label Dec 19, 2015
@mikeal
Copy link
Contributor

mikeal commented Dec 19, 2015

Personally, I think that this working group should live under the TSC, not the CTC (Core Technical Committee) which means we should ratify it in nodejs/tsc. The charter and project lifecycle allow us to have working groups directly under the TSC. This would be the first but I think that is where it belongs :)

Being that you'd be the first you'd actually be creating the WORKING_GROUPS.md file in nodejs/tsc :)

their identity.
+ Proactively seek and propose concrete steps the project can take to increase
inclusivity.
+ Serve as a resource for the development and enforcement of workflows that
Copy link
Member

Choose a reason for hiding this comment

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

I still have issues with the use of the word enforcement here. I recommend splitting this into two pieces and rewording to,

+ Serve as a resource for the development of workflows that protect community members and projects from harassment and abuse.
+ Work within the project and the community at large to ensure effective implementation of those workflows.

The issue with using enforcement is that it implies the ability to take punitive action and generally carries negative connotation.

@jasnell
Copy link
Member

jasnell commented Dec 19, 2015

I agree with @mikeal. The inclusivity working group should be chartered under the TSC not CTC. Recommend closing this PR and opening an equivalent in nodejs/TSC.

@ashleygwilliams
Copy link
Contributor Author

+1 for moving to the TSC. uno momento

@jasnell
Copy link
Member

jasnell commented Dec 20, 2015

hmm... the new PR doesn't actually add the Inclusivity WG details... did I miss something?

@ghost
Copy link

ghost commented Dec 20, 2015

@jasnell i think it's clarified here: nodejs/TSC#24 (comment)

@ashleygwilliams
Copy link
Contributor Author

yup, @sup, spot on. @jasnell, or anyone, can follow the inclusivity ratification process in this issue: nodejs/inclusivity#69. it is currently blocked by nodejs/TSC#24

@jasnell
Copy link
Member

jasnell commented Dec 20, 2015

OK, yep missed that one! Thanks @sup!

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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

get ratified by the TSC
5 participants