Gender Identity & Expression in the Code of Conduct #82
Comments
|
hey @Charlotteis thanks for filing! this is great and we'd love to help you with this effort. the first step will be to merge our own CoC, which i plan on finally doing today or tomorrow. plz share your thoughts! next will be writing a proposal via PR, would you be available to join us for our meeting next week on Thursday at 10am PST? |
|
oh good call @nebrius i was gonna mention that because @Charlotteis has good Opinions:tm: about such things |
|
also #65 :hint::hint::nudge:nudge: |
|
Cool, I see that the WG CoC would include gender identity, which is awesome. I'm going to go ahead and make a coffee and read Hi @nebrius 👋 , thanks so much for those links. As for 10am PST.... I'm usually on the train home from work at that time but I will certainly see what I can do! |
|
alright @ashleygwilliams I'm going I'm going (to #65). shambles over 😛 |
|
lol i was meaning to suggest to @Charlotteis that she czech it out to join! but yeah also lol it'd be great to ship a 1.0 version 🐬 |
|
@Charlotteis if you've got time to take a look, it'd be great to get your feedback on #74 as well |
|
Slowly going to go through everything.The WG README mentions 'gender and sex', should I open a new issue to discuss rewording this to 'gender identity (and expression) and sex'? |
|
Rust now includes this in their CoC (rust-lang/prev.rust-lang.org#270), which may be useful for our discussion here (only, as mentioned before, node seems to specifically mention how they used the Rust CoC) ✨ update though added, there seems to be some potential it could be removed. I'll know by Wednesday (20th January) |
|
A++ |
|
@nebrius I took a look at your Issue structure and rewrote my issue to adhere to it. Great work! I've also gone through all of the other issues/PR's linked and have commented on them where I felt it was needed :) |
|
Wow, thanks for all the feedback @Charlotteis, this is awesome! :) |
|
Hai! Rust just landed this: rust-lang/prev.rust-lang.org#288 |
|
Wait, can we just file a PR against nodejs/node with this change? I will +1 this patch myself, although it may end up landing in If this seems good, would @Charlotteis be interested in cooking up that PR and submitting it? If you're not comfortable doing so (because, understandably, there is always a chance for backlash), I would gladly volunteer for submitting it myself. |
|
+1 to just filing a PR against nodejs/node. I kinda have the feeling this should be pretty uncontroversial (to collaborators), since it doesn't change enforcement policies or anything and it was landed in Rust. |
|
Two things about this: I interpret this as a doc change and not a policy change. Being both a TSC (moderator) and CTC (policy owner) member. I'd prefer if someone besides myself was comfortable PRing it, but I will do it if necessary. |
Note: just because we used the Rust CoC originally makes no promises that we will follow it, but pointing this out won't hurt either. :) |
|
So I would love to have my name up there in the contributors, and I'm in half a mind to do it myself. However, I've already had some crappy experiences lately with regards to CoC changes (and lets not forget the current uproar in the community this week with this stuff) and would appreciate someone actually known with the Node community and known by Core to make this PR if that's possible. Thanks so much for all of this, I'm a very happy computer right now 💻 ✨ |
|
I'll cook one up, then. Stand by. |
|
🎉🎉🎉🎉🎉 |
rust-lang/prev.rust-lang.org#288 landed in the Rust repo so it seems like a good idea to just bring the updated list in. We also received a request to do this in nodejs/inclusivity#82 so this should resolve that. Thanks to [@Charlotteis](https://github.com/Charlotteis) for bringing up the original issue. Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Сковорода Никита Андреевич <[email protected]> PR-URL: nodejs#4801 Fixes: nodejs/inclusivity#82
|
a special thank you .gif for everyone's help with this <3 <3 |
rust-lang/prev.rust-lang.org#288 landed in the Rust repo so it seems like a good idea to just bring the updated list in. We also received a request to do this in nodejs/inclusivity#82 so this should resolve that. Thanks to [@Charlotteis](https://github.com/Charlotteis) for bringing up the original issue. Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Сковорода Никита Андреевич <[email protected]> PR-URL: #4801 Fixes: nodejs/inclusivity#82
rust-lang/prev.rust-lang.org#288 landed in the Rust repo so it seems like a good idea to just bring the updated list in. We also received a request to do this in nodejs/inclusivity#82 so this should resolve that. Thanks to [@Charlotteis](https://github.com/Charlotteis) for bringing up the original issue. Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Сковорода Никита Андреевич <[email protected]> PR-URL: #4801 Fixes: nodejs/inclusivity#82
rust-lang/prev.rust-lang.org#288 landed in the Rust repo so it seems like a good idea to just bring the updated list in. We also received a request to do this in nodejs/inclusivity#82 so this should resolve that. Thanks to [@Charlotteis](https://github.com/Charlotteis) for bringing up the original issue. Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Сковорода Никита Андреевич <[email protected]> PR-URL: #4801 Fixes: nodejs/inclusivity#82
rust-lang/prev.rust-lang.org#288 landed in the Rust repo so it seems like a good idea to just bring the updated list in. We also received a request to do this in nodejs/inclusivity#82 so this should resolve that. Thanks to [@Charlotteis](https://github.com/Charlotteis) for bringing up the original issue. Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Сковорода Никита Андреевич <[email protected]> PR-URL: nodejs#4801 Fixes: nodejs/inclusivity#82
rust-lang/prev.rust-lang.org#288 landed in the Rust repo so it seems like a good idea to just bring the updated list in. We also received a request to do this in nodejs/inclusivity#82 so this should resolve that. Thanks to [@Charlotteis](https://github.com/Charlotteis) for bringing up the original issue. Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Сковорода Никита Андреевич <[email protected]> PR-URL: nodejs#4801 Fixes: nodejs/inclusivity#82
rust-lang/prev.rust-lang.org#288 landed in the Rust repo so it seems like a good idea to just bring the updated list in. We also received a request to do this in nodejs/inclusivity#82 so this should resolve that. Thanks to [@Charlotteis](https://github.com/Charlotteis) for bringing up the original issue. Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Сковорода Никита Андреевич <[email protected]> PR-URL: nodejs#4801 Fixes: nodejs/inclusivity#82
rust-lang/prev.rust-lang.org#288 landed in the Rust repo so it seems like a good idea to just bring the updated list in. We also received a request to do this in nodejs/inclusivity#82 so this should resolve that. Thanks to [@Charlotteis](https://github.com/Charlotteis) for bringing up the original issue. Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Сковорода Никита Андреевич <[email protected]> PR-URL: nodejs#4801 Fixes: nodejs/inclusivity#82
Purpose
I'd really like to learn Node.js this year and to do that I usually try and get involved in a part of a community. Before I try and take part in a community, I generally look at the Code of Conduct first.
I noted that the Code of Conduct mentions 'gender' but that doesn't really feel like it includes non-binary or agender folk.
I realise the CoC says 'similar personal characteristic', but it feels like it'd be good to have things explicitly said rather than assumed. The Contributor Covenant has a lot of really useful things in it too (like age, technology choices, lack of religion), which we could consider co-opting things from.
Focus
This dicussion is specifically about including 'gender identity and expression' into the Node.js Code of Conduct. Discussions that don't consider including gender identity into the Code of Conduct should be considered off topic.
Some off topic examples include, but are not limited to:
Have a good day ✨
The text was updated successfully, but these errors were encountered: