Etiquette for posting comments
This question featured a quite heated discussion in the comments which led to some of them being removed. This action was discussed here and I have realized that our community lacks a guide about posting comments.
I would like for us to build together a list of topics we can include and avoid respectively, in the comments. These lists should stem from our Code of Conduct.
- requesting clarifications for the author. Examples: "what was the output of line X?", "can you include the stack trace?", "can you provide a reference for the second paragraph?"
- constructive criticism. Example: "why is foo() called twice?"
- +1 or thank you notes, if they also provide a little bit of information. Example: +1. This also worked with version X of the framework Y.
Should be avoided
- +1 or -1 with no explanation
- snarky comments. Example: "Codidact is not your personal assistant"
- references to overall author activity in the community. If you feel a user's activity is an issue, please use flagging instead of comments.
- providing full answers in the comments (they should be added as answers)
- secondary discussions or debates on controversial points (please ask a question on meta).
Please provide your suggestions about what is OK and not OK to include in the comments.
Once we have reached a fairly stable answer for this, I will include it in the help topics and use it as a reference for moderation.
Regarding "snark" - it is very hard and subjective to define. Our overall code of conduct says "be nice", but where do y …
Proposal: > Can Include > Helpful feedback I'd refrain from restricting the topic of feedback, because there ar …
> Should be avoided > > secondary discussions or debates on controversial points (please ask a question on meta). …
Proposal: > Can Include > A link to a chat room related to the question or answer. Even if tangentially. I've al …
Before posting this on the help pages, I will compile the feedback in a separate answer. Generally speaking, comments …