Update review_guidelines.md #47
Conversation
github-actions
bot
added
the
documentation
|
I feel that we should probably need some criteria for what can be posted - in case people game the system and try to amplify ads and then it would be somewhat awkward to say no. But we can add a general sentence that it should be reviewed/proof-read by a TSC member. |
| @@ -5,4 +5,5 @@ The review guidelines are currently under discussions. | |||
| Currently, only the following automated Bluesky content is allowed: | |||
|
|
|||
| - Posting of release announcements, or reposts of release announcements posted by releasers. | |||
| - Posts and Reposts of new features / website content / requests for community help or engagement, etc. | |||
There was a problem hiding this comment.
| - Posts and Reposts of new features / website content / requests for community help or engagement, etc. | |
| - Posts and Reposts of new features / website content / requests for community help or engagement, etc. | |
| - Should be proof-read/reviewed by at least 1 TSC member before being reposted. |
There was a problem hiding this comment.
We should clarify if we mean "at least x TSC voting members" or "a TSC motion"
There was a problem hiding this comment.
I think we should say "TSC voting member". I've added Triage role to @nodejs/tsc so we can request a review from the team
There was a problem hiding this comment.
IMO regular is also fine, just people who have been staying with the project for long enough to be trust-worthy to some extent.
There was a problem hiding this comment.
Would you also be fine with using "voting members" or "member of @nodejs/tsc"?
See conversation in #44