-
-
Notifications
You must be signed in to change notification settings - Fork 140
Moderation Policy: no bots but our bots #394
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
Conversation
MylesBorins
left a comment
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.
LGTM
|
@Trott we may want to do this in the admin repo The Moderation doc is living in two places. We likely should move this doc over there first |
|
@MylesBorins It's already there (I only figured that out on Friday myself, don't feel bad). @Trott -- you want to close this and move the proposal there? And should we start the process of removing the moderation policy here? It's at best confusing having it in two places, even if one of them is a deprecated repository. |
|
Also, on the proposal's merits: I think this is a sensible proposal, and also would be interested in basically codifying a "quick to ban, quick to forgive" policy around bots or any other behavior that can rapidly trigger events in repos, because it's so easy for bot-like activity to create a lot of work for a lot of people. |
|
I've opened #395 |
benjamingr
left a comment
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.
LGTMing to show agreement.
mhdawson
left a comment
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.
LGTM
|
This is going to have to be moved to the admin repo |
|
ping @nodejs/tsc @nodejs/moderation