-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Conversation
LGTM although I'm not sure if mine counts for this since I'm not TSC :) 🐑 |
pseudo-LGTM, also cc @nodejs/inclusivity |
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 Being that you'd be the first you'd actually be creating the WORKING_GROUPS.md file in |
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 |
There was a problem hiding this comment.
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.
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. |
+1 for moving to the TSC. uno momento |
hmm... the new PR doesn't actually add the Inclusivity WG details... did I miss something? |
@jasnell i think it's clarified here: nodejs/TSC#24 (comment) |
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 |
OK, yep missed that one! Thanks @sup! |
fixes nodejs/inclusivity#69