Moderation policy clarification around hiding comments
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Locate the moderation policy containing the quoted definitions and the Hide feature guidance. Review the surrounding policy language, then clarify whether hiding off-topic posts by non-Collaborators is outside the moderation-action requirements. Done means the policy clearly states the intended distinction without changing the existing guidance.
Written by the indexing model from the issue text.
Description
Our moderation policy says this:
Moderate means to modify, lock, or delete one or more Posts to correct or address Code of Conduct violations.
Note that it includes modify, lock, and delete, but not hiding. That was (IIRC) intentional. We want people to be able to hide off-topic comments without needing to engage in the overhead of opening an issue in the moderation repo or leaving a comment in the issue that they are hiding the comment in (as that defeats the purpose of hiding the comment in a lot of cases).
The policy also says:
Collaborators may use the Hide feature in the GitHub interface for off-topic posts by non-Collaborators.
We don't (as far as I see right now, at least) say that hiding off-topic posts by non-Collaborators is not considered a moderation action and therefore does not require the overhead of opening an issue in the moderation repo or otherwise announcing that you've moderated a comment.
If there's agreement that I have this right, then we should update the policy to amke that point clear.
@nodejs/moderation
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 13d 12h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nodejs/admin
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
tsc-agenda
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Issue-Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
sugarlabs/musicblocks#8924 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ArduPilot/ardupilot_wiki#8088 ·
-
[BUG] createTool tools cannot be registered with Mastra when exactOptionalPropertyTypes is enabled Opencustomer-eng status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100