I'm very sad to see you go and I want to thank you for being a hugely positive influence to this site in your elected tenure, your appointed tenure, before and in between.
I've learned incredibly much from you, both on a technical and a social level and I look forward to seeing you around the site :)
Thank you so much!
Thank you, rolfl!
There are too many things I feel thankful for when I think of you to list them all, but here are a notable few:
You have always been welcoming and kind to newcomers. I feel sure many new users of this site—like myself some years ago—have appreciated your guidance and have come back for more, or even stayed and became a regular as I have.
Ouch. And Thanks for all the bananas.
I have been watching all of this in the Moderator Chatroom with growing trepidation, but unable to articulate why.
But you just managed to say this way more eloquently than I could have managed.
Thanks so much for sharing you thoughts, and good luck to you.
Here I was hoping CR would survive this intact. Instead, a veteran moderator steps down. !@#$.
I don't blame you. I really don't. Given the circumstances and the risk you'd take by continuing, there's a lot of wisdom in your choice. Considering you're the wisest monkey I've ever seen, it's not unexpected to see you make the wise move.
We've seen you can ...
As already mentioned by @Jamal in the comments, StackExchange provides a Contact Form, as well as an Inbox shared by the community managers.
That being said, namecalling is not really liked in such cases. If you wish to raise a complaint against moderators (who are the trusted authority in the whole network), please consider carefully whether you might be ...
Remember, Comments are ephemeral ...
General Obsolete comments
The most common 'obsolete' comments on CodeReview are comments like:
Hi, and welcome to CodeReview. Your question is off-topic because your code is only available through a link. Please update your question with the actual code.
If you see comments like that, which are still around after ...
feeling sad to see you step down. I surely understand your reasons but hope you stick around. That beeing said, thanks a lot for endless hours of keeping the site running. See you in the 2nd monitor
I think these questions (off-topic, old, highly viewed) ought to be tracked and closed. They date back from an age of darkness, when the site's scope wasn't as clear-cut as it is today.
If they're valuable content with some upvoted answers, then perhaps we should put a historical lock on them. I have flagged the question you've mentioned as such.
As a beta ...
This specific question is directed toward 200_success, but I think the point you are raising is independent of that.
Let's break down your question in to what I think are the relevant parts:
Is there a concept of a super-mod in Code Review - do we have a 'hierarchy'?
Is there a policy from the mods for closing/reopening things that the community is not ...
We are looking for answers that provide insightful observations about the code in the question. Answers that consist of independent solutions with no justification do not constitute a code review, and may be removed.
These specific cases
What happened in these specific cases (and what happened to the flags) is pretty simple. The comments got deleted.
Unsubstantiable accusations of vote abuse are a violation of assuming best intentions until proven otherwise. As such these comments are just noise and therefore deleted.
In the first case (the ruby question), pulling ...
There's no need to flag every time you remove cursing. You should only flag if there's a problem that requires moderator attention. Individual cases of cursing does not warrant this, especially as it can be simply edited out if it's bad enough.
If you've been noticing it from a particular user, and they refuse to stop if it's indeed a serious matter (...
Lock the question as soon as it is answered. Sound a bit too drastic.
Locking is a moderator tool with good reason. For one the lock mechanism implemented by SE currently only allows completely locking a post, which would preclude any subsequent answers.
As it currently stands this is not feasible, especially since there are valid reasons for editing a ...
First of all, I appreciate the feedback. While good moderators can strengthen a site, bad ones (whether deliberate or unwitting) can be toxic. If any community member is unhappy with a moderator action, I'd much rather know about it.
Second, moderators do make mistakes. Community members do too — sometimes five of them together. ...
Should any answer that has a Moderator Notice be flagged again?
That's still okay to do. It'll make the community more aware of it via the review queue, and it'll leave more of a mark on the answer (it's not so easy keeping track of post notices). Applying a post notice is quicker and the moderator may not be monitoring the post closely for any changes. ...
Classic auto-comments text
You have presented an alternative solution, but haven't reviewed the code. Please explain your reasoning (how your solution works and how it improves upon the original) so that the author can learn from your thought process.
A mod notice might be a little more like an order than a request, so the please might ...
In general, comments are ephemeral.... they are not designed to have long-lasting content. Comments are to seek clarification on posts, and point out short term issues. Once the issues are addressed, the comments should be removed.
In the case of this specific question, things became a real mess.... in part, because the question started off "broken", and ...
There is no good answer to this question.
This answer to another on-off-topic-question somehow seems relevant.
It is purely subjective, and based on impressions, and expectations, and prejudices.
If a question comes along (Billy), and it says:
Here's my code, it works well. Please review it, and, by the way, if you can think of a way to make it do ...
I gave my rationale in a comment when I migrated the question. Identifiers such as ScriptIAmMaking and test are placeholders akin to foo and bar, making it example code and therefore off-topic for Code Review. Are those identifiers peripheral to the question? I didn't make that distinction at the time, as the question didn't obviously state what code was ...
In my opinion, yes the plain English matters. It matters a lot. That's the part of the question that explains not just the code, but the intention of the OP. It's not just the code in the question that makes it on topic or not. It's the intention of the asker as well. Take this meta for example. The code itself is (debatably) reviewable, but it's not asking ...
I know that some questions that are migrated a long time ago, don't retain the migrated mark for all eternity, I have noticed this on other sites as well.
taking that into consideration, those votes and answers may have come from StackOverflow.
another point to address is that this person posted someone else's code here.
They could be Violating Licensing ...
All flags raise a warning for moderators in the top bar of the site. The Not An Answer flags behave the same way as all other flags.
The Not An Answer flags could probably be handled by the community. The community already participates in the moderation of such cases, and this can be seen in the linked answer. That is, low quality answers enter the Low ...
You are bringing up multiple different suspects and there's many things I'd like to say, I will try to print down some of them here:
Asking a good question with code from a commercial project is hard and takes a lot of effort to make it fit this site. Only few people go through this effort to do that.
While we would love it if an asker ...
Your question is self-contradicting.
If an off-topic question gets a good answer, is the question on-topic?
That's what you are asking, and the answer is no. A question can not be both off topic, and on topic.
So, if someone posts a good answer on a question that:
links to off-site code (github, pastebin)
someone else's code
a request for ...
Basically, the gist of this is, we should be having discussions on the meta before overturning a close vote on a question that has received no edits since the close vote, right? At the barest of minimums, the re-opening moderator needs to leave a comment on the question explaining why the close reason voted on doesn't apply to the question.
I don't think we ...
Speaking as a private contributor, rather than as a moderator…
Our mission is to review code or to have our code reviewed. Any other activity is a distraction from that goal.
Of course, some overhead is unavoidable, to ensure that the community is aligned and happy.
Closing off-topic questions is necessary to maintain quality. However, open questions ...
Whether a flag is needed depends on whether you think the issue merits moderator attention.
The Stack Exchange system is designed so that many of the moderation tasks can be handled by a community of high-reputation users. If it looks like editing the question solved the problem, then moderator intervention would be unnecessary. On the other hand, if ...
Too large or complex. More than 300 lines (we can debate the level) of code is bordering on unmanageable in a CR context. How many "real things" can you do in 300 lines?
No, we allow more than 300 lines of code. In fact we close questions without enough code and have had our post character limit increased to do so.
Proprietary. The author is not ...