Update code of conduct to clarify reporting and moderation #5107
Conversation
| reported by: | ||
|
|
||
| * Emailing [[email protected]](mailto:[email protected]) (this will email all TSC members) | ||
| * Contacting [individual TSC members](https://nodejs.org/en/foundation/tsc/#current-members-of-the-technical-steering-committee). |
There was a problem hiding this comment.
Is there a better place I can link people for contact info for the TSC or is the right thing?
There was a problem hiding this comment.
Uh, looks like that's on me, not yet, but: nodejs/TSC#1
There was a problem hiding this comment.
I'll leave it alone for now. We can change it when that lands.
There was a problem hiding this comment.
Isn't an email to [email protected] the way to go? Individual TSC members may have different ideas on how to deal with an issue so contacting one individually may lead to a certain level of arbitrariness.
There was a problem hiding this comment.
This is just explicitly repeating the contact guidelines in the moderation policy.
There was a problem hiding this comment.
Okay, filed an issue for that: nodejs/TSC#45
Fishrock123
added
doc
|
Heya, could you make sure the commit messages are max 50 chars and the descriptions are max 72? Also I think the latter 3 commits could probably be squashed into one. Seems fine to me otherwise. The contact details definitely need to be easily accessible. |
|
LGTM (if suggested fixes are included) |
|
@Fishrock123 Sorry bout that. Was doing this quickly in the github UI and the commits were a little more quick and dirty than they should be. Will pull it down, clean things up a bit, and update shortly. |
Clarifies the code of conduct by making the following changes: - Adds section headings to make it easier to quickly parse. - Adds easy to find contact information. - Adds link to TSC moderation policies. - Moves attribution to the bottom of the page.
|
I squashed it all into one commit since it's a pretty small change and modified the commit message to match the contribution guidelines. Is "doc" the right subsystem to list in the first line or should it be something else? Happy to change it something else if there's a specific thing I should use for policy documentation like this. |
|
@juliepagano Nah, we usually just use |
mscdex
removed
the
meta
|
LGTM |
| @@ -1,8 +1,6 @@ | |||
| ## Code of Conduct | |||
|
|
|||
| This Code of Conduct is adapted from [Rust's wonderful | |||
| CoC](http://www.rust-lang.org/conduct.html) as well as the | |||
| [Contributor Covenant v1.3.0](http://contributor-covenant.org/version/1/3/0/). | |||
|
LGTM |
1 similar comment
|
LGTM |
|
Thanks, landed in 1e146e7 |
Clarifies the code of conduct by making the following changes: - Adds section headings to make it easier to quickly parse. - Adds easy to find contact information. - Adds link to TSC moderation policies. - Moves attribution to the bottom of the page. PR-URL: #5107 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Kat Marchán <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Jeremiah Senkpiel <[email protected]>
Clarifies the code of conduct by making the following changes: - Adds section headings to make it easier to quickly parse. - Adds easy to find contact information. - Adds link to TSC moderation policies. - Moves attribution to the bottom of the page. PR-URL: #5107 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Kat Marchán <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Jeremiah Senkpiel <[email protected]>
Clarifies the code of conduct by making the following changes: - Adds section headings to make it easier to quickly parse. - Adds easy to find contact information. - Adds link to TSC moderation policies. - Moves attribution to the bottom of the page. PR-URL: #5107 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Kat Marchán <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Jeremiah Senkpiel <[email protected]>
Clarifies the code of conduct by making the following changes: - Adds section headings to make it easier to quickly parse. - Adds easy to find contact information. - Adds link to TSC moderation policies. - Moves attribution to the bottom of the page. PR-URL: #5107 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Kat Marchán <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Jeremiah Senkpiel <[email protected]>
Clarifies the code of conduct by making the following changes: - Adds section headings to make it easier to quickly parse. - Adds easy to find contact information. - Adds link to TSC moderation policies. - Moves attribution to the bottom of the page. PR-URL: #5107 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Kat Marchán <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Jeremiah Senkpiel <[email protected]>
Clarifies the code of conduct by making the following changes: - Adds section headings to make it easier to quickly parse. - Adds easy to find contact information. - Adds link to TSC moderation policies. - Moves attribution to the bottom of the page. PR-URL: #5107 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Kat Marchán <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Jeremiah Senkpiel <[email protected]>
Clarifies the code of conduct by making the following changes: - Adds section headings to make it easier to quickly parse. - Adds easy to find contact information. - Adds link to TSC moderation policies. - Moves attribution to the bottom of the page. PR-URL: nodejs#5107 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Kat Marchán <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Jeremiah Senkpiel <[email protected]>
This PR:
This PR was prompted by the inclusivity WG being notified that someone was having trouble figuring out who to report an incident to. Hopefully this will make that information easier to find.