SE Code Review Close Questions room

@SimonForsberg Closing sooner prevents people from answering bad questions and making the mess harder to clean up.

Announcement: New chat room CRCQR

There was a period where it was mostly me chatting with myself, so I kind of gave up on this room.

If you encounter a post that Lacks description of what the code is doing, please vote to close as "Unclear what you are asking"

@GenericBot Considering how little this room is used, maybe it should ?

Why are you talking about Stack Overflow in a Code Review chat room?

7) The list should have now collapsed, and the target room setting should contain the name of this room. Open it again. 8) [Optional] Now, there are some junk rooms left there, possibly the "The Stack Exchange Network" room twice. For each of those useless rooms, click the "-" button to the right of the room's name, and, if you're not done, open the target room setting again. 9) You're ready to go!

Don't forget to comment, people.

Since the last time this room was actually used was in September of last year (which is basically half a year ago), I'm freezing this room for now

Nobody here?

keep alive

@MartinR https://www.youtube.com/watch?v=bCDIt50hRDs

@t3chb0t If you're properly lazy, you'll want the Close Votes userscript, so you won't need to type very much at all!

And I've upvoted Martin's comment - let's try to be welcoming, and assume good intent.

I routinely whip questions into shape if the information is already there, but not in our preferred form. I'd rather not hassle newbies over formalities any more than necessary.

PSA: If you want to contribute to the github repo for the faq, please shoot me a message with your GH username

if i were a newbie, i'd prefer to know why i'm getting downvotes or close votes, so the comments would be appreciated :)

For those who are ROs, I recommend reading A guide to moderating chat.

Just hope we don't make it worse trying to make it better.

People, don't forget to leave a comment on a bad question so others can easily identify why/whether it's bad. Two standard comments I often use:

@gparyani Nice you found the only chat channel I am available at the moment :-D.

ROs: Version 3.2.0 of the Request Archiver has been released (GitHub) (install). It adds support for the Archiver scan in CRCQR, CRUDE, and The Tavern, along with various other improvements and bug fixes. You should find two additional buttons "archiver" and "scan 3k" next to the chat input area. Scanning is based on # of messages. "scan 3k" scans back 3000 messages from current.

Request types the alpha version supports: for questions: cv-pls; del-pls; reopen-pls; undel-pls; "revisit (in 2 days)"; "revisit (in 11 days)"; "revisit (in N days)"; reflag VLQ; flag-pls spam; flag-pls offensive. For answers: all of those except cv-pls and reopen-pls. For suggested edits it does: review-pls.

The "revisit" request types set an automatic revisit to the post after the amount of time you select. The next time you open a Stack Exchange question page after that time a new tab will be automatically opened with the post you have set to revisit. You can use the request reason to leave yourself a note about why you are revisiting the post.

There's an alpha version of the Request Generator, v1.8.5.0, (GitHub) (install) available with support for more request types. The alpha version does not work with Greasemonkey 4 on Firefox. It works fine with Tampermonkey and Violentmonkey on all browsers.

@SᴀᴍOnᴇᴌᴀ plus salsa :-P

@πάνταῥεῖ The basic SE interface for moving messages is "room" (in sidebar, just below the room blurb)➞"move messages" you can then click on messages to select them. After you've selected the ones you want, then click "relocate" in the popup that opened. I'll try to get an update for the Archiver out today which makes it a bit easier, and allows message selection from the transcript, search, and user pages.

@πάνταῥεῖ Messages can only be edited by the user posting them (for 2 minutes) and by moderators. Your only option as an RO is to move it to a different room (e.g. /dev/null, as the Graveyard is for complete or expired requests).

> Coming Soon: CRBotics

Here's what I proposed as the FAQ so far: github.com/CodeReviewCommunity/SECRCVR/blob/master/FAQ.md

How to initialize the SE Close Vote Request Generator: 1) Make sure the userscript is installed and enabled. 2) Go to a question. 3) Click the "cv-pls" button at the bottom of the question. 4) Click the second item from the list that pops. This is the target room setting. It may read "The Stack Exchange Network". 5) Paste this exact string into the text box: https://chat.stackexchange.com/rooms/85306/. 6) Click the "Set" button.

@πάνταῥεῖ Looks very concrete to me. Answered.

@t3chb0t We carefully need to distinguish established requests from mere discussions here.

my 2 cents is if you find something wrong with the question enough to post it in a close review room, you should probably comment why the post needs work so OP is aware :p

@Peilonrayz Good job with the comments lately. Keep it up. Just a small note: If a question doesn't fit anywhere on SE (like these two last questions), recommending other Stack Exchange sites just risks the OP to have another bad experience, on Stack Overflow or Software Engineers or whereever.

That makes sense, we're still in an infancy atm

We don't close questions because we dislike questions. We close crap to give the rest a chance.