| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
LGTM although I'm not sure if mine counts for this since I'm not TSC :) 🐑 |
Sorry, something went wrong.
|
pseudo-LGTM, also cc @nodejs/inclusivity |
Sorry, something went wrong.
|
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 :) |
Sorry, something went wrong.
There was a problem hiding this comment.
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.
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
|
+1 for moving to the TSC. uno momento |
Sorry, something went wrong.
|
hmm... the new PR doesn't actually add the Inclusivity WG details... did I miss something? |
Sorry, something went wrong.
|
@jasnell i think it's clarified here: nodejs/TSC#24 (comment) |
Sorry, something went wrong.
|
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 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
fixes nodejs/inclusivity#69