Skip to main content
7 events
when toggle format what by license comment
Dec 6, 2015 at 13:21 comment added rolfl I completely agree with Robert. I use both Stack Overflow, and Code Review, and adding a new, complicated close reason to Stack Overflow will create more uncertainty, and mess. The issuse is not about teaching SO users when to recommend Code Review. The issue is educating them to use the close reasons they already have. I frankly think that Duga has done quote well, and the issues is not one of SO folk needing something different, the issue is one of there simply being so many SO users that it is inevitable that this will continue to happen - regardless of what close reasons are available
Dec 6, 2015 at 7:01 comment added 200_success Mod We've tried educating users one at a time as Duga reports them. It's futile. Sometime it even escalates into minor flame wars when an SO user accuses us of being pedantic or even wrong. You're essentially saying that the status quo is fine, and we think it isn't.
Dec 6, 2015 at 6:46 history edited Robert Harvey CC BY-SA 3.0
added 13 characters in body
Dec 6, 2015 at 6:43 comment added Robert Harvey Then change my wording from "Migration" to "Suggested Migration" (which is what your new close reason essentially is), and everything I said still holds. The purpose of close reasons is to close questions, not kill memes, and people suggesting that bad questions be moved to CR is an educational problem, not a technical one.
Dec 6, 2015 at 6:42 comment added 200_success Mod On a technical level, you're right that there is a Too Broad close reason. However, it is unintuitive, which has led to the harmful and bogus "belongs on Code Review" custom close reason. You haven't suggested a better way to kill the meme.
Dec 6, 2015 at 6:41 comment added 200_success Mod We already recognize that an SO → CR migration path would be disastrous given the current situation.
Dec 6, 2015 at 6:34 history answered Robert Harvey CC BY-SA 3.0