3
\$\begingroup\$

Closing for migration is a bit tough. Right now, if you don't want to send the post to SU or meta, you have to move back up the close tree.

My suggestion is to add a manual "other" option to the off topic -> migration option.

Of course, the default is where it seems to be going right now, which is a generic "unclear what you're asking" path, which is simply the easiest, requiring nothing but a selection and no typing, but this doesn't feel right.

I'm not quite sure how the act of migrating actually interfaces with the close choice, but I think this is one of those small things that make review chores a bit more tedious for those who choose to do them. I find myself clicking skip more often, lately.

\$\endgroup\$
13
  • \$\begingroup\$ You can close for "off topics" and one of the sub-choices is "this question belongs on a different stack exchange site." But then the only choices for places to migrate are superuser or Meta.EE. (While it seems to me the most common places we need to migrate are Arduino and DIY) \$\endgroup\$
    – The Photon
    Commented Jan 26, 2015 at 18:35
  • \$\begingroup\$ We're not obligated to fix it for someone that can't be bothered to post in the right place. Just close it and move on. If there isn't a close reason that seems to fit, pick the nearest handy one. Again, it's not worth wasting our time fixing someone else's stupidity. If they aren't told exactly why their question was closed, oh well. They could try reading the rules and learning the site better before blurting out a question next time. Kicking people like that in the butt as they're being thrown out is a Good Thing. \$\endgroup\$
    – Olin Lathrop
    Commented Jan 26, 2015 at 18:41
  • \$\begingroup\$ @ThePhoton -- that's the point -- the "different exchange" option is gone. It was there a few days ago, but I can't see it. \$\endgroup\$
    – Scott Seidman
    Commented Jan 26, 2015 at 18:50
  • \$\begingroup\$ @Scott re: Your second paragraph. I can still see the off-topic → belongs on another site in the Stack Exchange network option on a fresh post. May be I can see it only because I have moderator access. The questions older than 60 days can not be migrated [as an aside, I question that policy myself]. Possibly, when you didn't find the migration option, you were looking at an old question. \$\endgroup\$
    – Nick Alexeev Mod
    Commented Jan 26, 2015 at 18:53
  • \$\begingroup\$ @NickAlexeev, When I look at one, the only migration options are Superuser and Meta. There's no "fill-in-the-blank" choice. So this option is useless if Superuser or Meta isn't the migration target. \$\endgroup\$
    – The Photon
    Commented Jan 26, 2015 at 19:01
  • \$\begingroup\$ @NickAlexeev -- right you are!! I'll edit later and catch this up to reality. The original intent was to say how the current migrate options miss the mark, and an "other" manual field would be cool. Then I pulled up an old example, and came to a wrong conclusion! \$\endgroup\$
    – Scott Seidman
    Commented Jan 26, 2015 at 19:13
  • 2
    \$\begingroup\$ @ThePhoton -- I agree, but somewhat disagree with the "useless" part. I think its less than useless, as by the time you come to that conclusion you've moved down a tree to a dead end, and have to go back up the tree. Just poor user interfacing, which I'd think SE would rather avoid. \$\endgroup\$
    – Scott Seidman
    Commented Jan 26, 2015 at 19:15
  • 1
    \$\begingroup\$ @ScottSeidman, totally agree. I believe the UX guys call this a "misaffordance". \$\endgroup\$
    – The Photon
    Commented Jan 26, 2015 at 19:17
  • 1
    \$\begingroup\$ @OlinLathrop If none of the close reasons apply, you are probably closing a valid question. \$\endgroup\$
    – markrages Mod
    Commented Jan 26, 2015 at 20:13
  • \$\begingroup\$ @mark: Sometimes questions are just crap. They may not fit a official close reason, but they still need to be closed. For example, lots of lower case "i", text speak, painful formatting, no periods, no capitalization of first letters, etc. No, they shouldn't be edited to let the asker slide by and get away with gross disrespect. Sometimes the catch-all unclear applies, but not always. \$\endgroup\$
    – Olin Lathrop
    Commented Jan 26, 2015 at 22:22
  • \$\begingroup\$ @The Photon: There's actually more to it than misaffordance. Misaffordance is the part you go into the migration menu only to see that there's nothing useful there. The worst part (for me) is where you "lose your work" by having to go back all the way to beginning of the close-voting process. I forgot what's the name for that in the usability jargon (if I ever knew it). \$\endgroup\$
    – got trolled too much this week
    Commented Oct 7, 2015 at 5:11
  • \$\begingroup\$ @RespawnedFluff Maybe we should ask on the User Experience stack \$\endgroup\$
    – Scott Seidman
    Commented Oct 7, 2015 at 10:41
  • 1
    \$\begingroup\$ @Scott Seidman: ux.stackexchange.com/questions/85496/… \$\endgroup\$
    – got trolled too much this week
    Commented Oct 7, 2015 at 11:04

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .