Comments (3)
Prior to wordsmithing to get something succinct we can put in the FAQ, I think we might benefit by making sure we're all on the same page and also have something more detailed, so we're sure we're not leaving out anything important from the more succinct version.
Pinging can be interpreted in a couple of different ways. As we all know, a "ping" occurs when either using @username
, or replying to an existing message. Unless we are specific, people will, and have, interpreted it both ways with respect to this issue. Very broadly, I think what we're trying convey is: "Don't drag a mod into talking about specific moderation issues."
More specifically, I think what we're trying to get across is:
- it's fine to:
- Engage mods in conversation (using "reply", which causes pings, or explicitly
@[mod]
) about general topics, just like any SO user. However, don't over do it, as Mods always have other things which they could be doing on SO, but that doesn't mean they're not human and uninterested in other things (or, so we think :-) ). - Use reply/ping to continue a conversation begun by the Mod, or willingly joined by the Mod, about moderation topics, including things which would normally be handled with a flag (e.g. Mod comes into SOCVR asking for help checking for plagiarism).
- Engage mods in conversation (using "reply", which causes pings, or explicitly
- It's not acceptable to:
- Change the topic of a conversation with a mod to a matter which would normally be handled by a flag, when the issue is not directly related to the current conversation.
- Ping a Mod to initiate a conversation about something which can be handled by a flag or meta post.
In other words, it's not acceptable to impose upon the mod by asking them to deal directly with things which should be handled with flags (or meta posts), just because the mod is currently in, or has been in, SOCVR.
There also appears to be a disparity in style as to how to express this in the FAQ: either having a general statement of purpose, or a list of specific things. Both approaches have their benefits and drawbacks. A more general statement allows us to be less specific, with the implicit expectation that people should use their own judgement. With a list, people will often start thinking about corner cases. In both cases, we should probably have something like: "If in doubt, ask the room what the appropriate thing to do is."
from room-meeting-topics.
I agree with the intent but couldn't this be simplified?
Consider moderators in the room as being on leisure time. Do not ping them for issues related to Stack Overflow moderation or support, use flags like any other SO user.
from room-meeting-topics.
How about this?
- Pinging mods engaged in general conversation is acceptable
- Pinging mods for anything that could be handled with a flag is not acceptable
- Ask the room about how to handle non-flag moderation problems
from room-meeting-topics.
Related Issues (20)
- Do we need *Do not request action on a post that you have asked or answered, or for an edit which you have made* HOT 4
- Should we wait until after the grace period is over before posting a cv-pls request? HOT 1
- Should it be allowed to systematically target questions that are answered by a specific OP HOT 2
- Can we revisit a rule or FAQ about prescribed close reasons? HOT 4
- Revisit the use of the term "crap" HOT 1
- Should users be allowed to request action on posts they are involved in? HOT 8
- Should 'bad' or 'wrong' *-pls requests be binnable with some 3rd party user consensus? HOT 6
- Off-topic chatter should not be allowed, only messages with *-pls requests are welcome HOT 4
- Should SOCVR encourage cleanup of canonical questions? HOT 2
- Should (limited) re-posting of an expired *-pls request be allowed?
- How should we deal with requests related to Meta discussions? HOT 1
- When should queues be allowed to avoid the "recent" rule? HOT 3
- FAQ page rewrite HOT 4
- What should be done with cv-pls requests from <3k users? HOT 3
- Should the room name be dropped from the burnination posts? HOT 4
- Evaluate actions, if any, that should be taken in regard to the change in close votes threshold HOT 4
- If a strike would be organized on Stack Overflow should SOCVR participate? HOT 5
- "has no value to stay on site" is not a valid delete reasons HOT 6
- Can the cv-pls request reasons be abbreviated and if yes, what should they be? HOT 2
- Should users be allowed to post del-pls requests for their own answers which they cannot self-delete
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from room-meeting-topics.