13 replaced http://stackoverflow.com/ with https://stackoverflow.com/
source | link

Possible Duplicate:
More options when flagging for migration

When flagging http://stackoverflow.com/questions/9941749/how-to-boost-module-cron-run-or-savehttps://stackoverflow.com/questions/9941749/how-to-boost-module-cron-run-or-save as off topic on SO (following Which questions should be on-topic on Drupal Answers, but not on Stack Overflow? since is didn't involve any programming) I was missing the "belongs on drupal.stackexchange.com" option.

The "only" options were:

  • is off topic
  • meta.stackoverflow.com
  • serverfault.com
  • superuser.com
  • webmasters.stackexchange.com
  • programmers.stackexchange.com

Having a couple of suggestions left me with the impression that I should be explicit when flagging, and made me backtrack and leave an apologetic "it needs ♦ moderator attention" comment.

With so many sites coming out of beta, how can we improve this UI?

Even more options?

I think an extra option with a select box with all sites out of beta (perhaps minus the options that already have their own radio), could fix this. See this question for a mockup along these lines.

I'm not for removing the radio's with the best guesses of the system, just an extra option for when the guessing fails.

As @lix commented on the question, having all sites enumerated is impractical. But I still think having some pre-guessed options (4?) and a "catch-all" selectbox-option, could work.

Like suggested to More options when flagging for migration, this is growing more and more above the "Don't Make Me Think" barrier and might just not work. A huge select is not any different from a long list of radio-buttons.

Fewer options?

One of the related questions I didn't find until @bart pointed them out was answered that moderators already have a great migration UI (see also @fabian's comment or Should some communities have more than 4 migration targets? for a screenshot of the Vote-to-close dialog).

That being the case, I'd opt for just 2 options

  • off-topic
  • belongs on another SE site. If you know it is a better fit for that site, please leave a comment on the question roughly following this template: Hi $name, I think your question would be a better fit on $site. This site deals with $topic. Please don't cross-post, a mod will migrate it for you.

Expanding the faq?

Given all the linked questions I think I'm not the only one confused by the current UI. If an intuitive UI is impossible, we could at least improve the faqfaq, to prevent yet another duplicate post on meta, like this one. The accepted answer to the original feature request Can we have "belongs on some other stackexchange site" as an option when voting to close? is short, yet already clarifying.

Or perhaps, that's one of meta's functions, and we should change the AnalyticalAnalytical-badge to "Read every question on meta" ;-)

Possible Duplicate:
More options when flagging for migration

When flagging http://stackoverflow.com/questions/9941749/how-to-boost-module-cron-run-or-save as off topic on SO (following Which questions should be on-topic on Drupal Answers, but not on Stack Overflow? since is didn't involve any programming) I was missing the "belongs on drupal.stackexchange.com" option.

The "only" options were:

  • is off topic
  • meta.stackoverflow.com
  • serverfault.com
  • superuser.com
  • webmasters.stackexchange.com
  • programmers.stackexchange.com

Having a couple of suggestions left me with the impression that I should be explicit when flagging, and made me backtrack and leave an apologetic "it needs ♦ moderator attention" comment.

With so many sites coming out of beta, how can we improve this UI?

Even more options?

I think an extra option with a select box with all sites out of beta (perhaps minus the options that already have their own radio), could fix this. See this question for a mockup along these lines.

I'm not for removing the radio's with the best guesses of the system, just an extra option for when the guessing fails.

As @lix commented on the question, having all sites enumerated is impractical. But I still think having some pre-guessed options (4?) and a "catch-all" selectbox-option, could work.

Like suggested to More options when flagging for migration, this is growing more and more above the "Don't Make Me Think" barrier and might just not work. A huge select is not any different from a long list of radio-buttons.

Fewer options?

One of the related questions I didn't find until @bart pointed them out was answered that moderators already have a great migration UI (see also @fabian's comment or Should some communities have more than 4 migration targets? for a screenshot of the Vote-to-close dialog).

That being the case, I'd opt for just 2 options

  • off-topic
  • belongs on another SE site. If you know it is a better fit for that site, please leave a comment on the question roughly following this template: Hi $name, I think your question would be a better fit on $site. This site deals with $topic. Please don't cross-post, a mod will migrate it for you.

Expanding the faq?

Given all the linked questions I think I'm not the only one confused by the current UI. If an intuitive UI is impossible, we could at least improve the faq, to prevent yet another duplicate post on meta, like this one. The accepted answer to the original feature request Can we have "belongs on some other stackexchange site" as an option when voting to close? is short, yet already clarifying.

Or perhaps, that's one of meta's functions, and we should change the Analytical-badge to "Read every question on meta" ;-)

Possible Duplicate:
More options when flagging for migration

When flagging https://stackoverflow.com/questions/9941749/how-to-boost-module-cron-run-or-save as off topic on SO (following Which questions should be on-topic on Drupal Answers, but not on Stack Overflow? since is didn't involve any programming) I was missing the "belongs on drupal.stackexchange.com" option.

The "only" options were:

  • is off topic
  • meta.stackoverflow.com
  • serverfault.com
  • superuser.com
  • webmasters.stackexchange.com
  • programmers.stackexchange.com

Having a couple of suggestions left me with the impression that I should be explicit when flagging, and made me backtrack and leave an apologetic "it needs ♦ moderator attention" comment.

With so many sites coming out of beta, how can we improve this UI?

Even more options?

I think an extra option with a select box with all sites out of beta (perhaps minus the options that already have their own radio), could fix this. See this question for a mockup along these lines.

I'm not for removing the radio's with the best guesses of the system, just an extra option for when the guessing fails.

As @lix commented on the question, having all sites enumerated is impractical. But I still think having some pre-guessed options (4?) and a "catch-all" selectbox-option, could work.

Like suggested to More options when flagging for migration, this is growing more and more above the "Don't Make Me Think" barrier and might just not work. A huge select is not any different from a long list of radio-buttons.

Fewer options?

One of the related questions I didn't find until @bart pointed them out was answered that moderators already have a great migration UI (see also @fabian's comment or Should some communities have more than 4 migration targets? for a screenshot of the Vote-to-close dialog).

That being the case, I'd opt for just 2 options

  • off-topic
  • belongs on another SE site. If you know it is a better fit for that site, please leave a comment on the question roughly following this template: Hi $name, I think your question would be a better fit on $site. This site deals with $topic. Please don't cross-post, a mod will migrate it for you.

Expanding the faq?

Given all the linked questions I think I'm not the only one confused by the current UI. If an intuitive UI is impossible, we could at least improve the faq, to prevent yet another duplicate post on meta, like this one. The accepted answer to the original feature request Can we have "belongs on some other stackexchange site" as an option when voting to close? is short, yet already clarifying.

Or perhaps, that's one of meta's functions, and we should change the Analytical-badge to "Read every question on meta" ;-)

12 replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
source | link

Possible Duplicate:
More options when flagging for migrationMore options when flagging for migration

When flagging http://stackoverflow.com/questions/9941749/how-to-boost-module-cron-run-or-save as off topic on SO (following http://meta.stackexchange.com/questions/87719/which-questions-should-be-on-topic-on-drupal-answers-but-not-on-stack-overflowWhich questions should be on-topic on Drupal Answers, but not on Stack Overflow? since is didn't involve any programming) I was missing the "belongs on drupal.stackexchange.com" option.

I think an extra option with a select box with all sites out of beta (perhaps minus the options that already have their own radio), could fix this. See this questionthis question for a mockup along these lines.

As @lix commented on the question, having all sites enumeratedall sites enumerated is impractical. But I still think having some pre-guessed options (4?) and a "catch-all" selectbox-option, could work.

Like suggested to More options when flagging for migrationMore options when flagging for migration, this is growing more and more above the "Don't Make Me Think" barrier and might just not work. A huge select is not any different from a long list of radio-buttons.

One of the related questions I didn't find until @bart pointed them out was answeredanswered that moderators already have a great migration UI (see also @fabian's comment or http://meta.stackexchange.com/questions/118685/should-some-communities-have-more-than-4-migration-targetsShould some communities have more than 4 migration targets? for a screenshot of the Vote-to-close dialog).

Given all the linked questions I think I'm not the only one confused by the current UI. If an intuitive UI is impossible, we could at least improve the faq, to prevent yetyet anotheranother duplicate post on meta, like this one. The accepted answeraccepted answer to the original feature request http://meta.stackexchange.com/questions/48662/can-we-have-belongs-on-some-other-stackexchange-site-as-an-option-when-votingCan we have "belongs on some other stackexchange site" as an option when voting to close? is short, yet already clarifying.

Possible Duplicate:
More options when flagging for migration

When flagging http://stackoverflow.com/questions/9941749/how-to-boost-module-cron-run-or-save as off topic on SO (following http://meta.stackexchange.com/questions/87719/which-questions-should-be-on-topic-on-drupal-answers-but-not-on-stack-overflow since is didn't involve any programming) I was missing the "belongs on drupal.stackexchange.com" option.

I think an extra option with a select box with all sites out of beta (perhaps minus the options that already have their own radio), could fix this. See this question for a mockup along these lines.

As @lix commented on the question, having all sites enumerated is impractical. But I still think having some pre-guessed options (4?) and a "catch-all" selectbox-option, could work.

Like suggested to More options when flagging for migration, this is growing more and more above the "Don't Make Me Think" barrier and might just not work. A huge select is not any different from a long list of radio-buttons.

One of the related questions I didn't find until @bart pointed them out was answered that moderators already have a great migration UI (see also @fabian's comment or http://meta.stackexchange.com/questions/118685/should-some-communities-have-more-than-4-migration-targets for a screenshot of the Vote-to-close dialog).

Given all the linked questions I think I'm not the only one confused by the current UI. If an intuitive UI is impossible, we could at least improve the faq, to prevent yet another duplicate post on meta, like this one. The accepted answer to the original feature request http://meta.stackexchange.com/questions/48662/can-we-have-belongs-on-some-other-stackexchange-site-as-an-option-when-voting is short, yet already clarifying.

Possible Duplicate:
More options when flagging for migration

When flagging http://stackoverflow.com/questions/9941749/how-to-boost-module-cron-run-or-save as off topic on SO (following Which questions should be on-topic on Drupal Answers, but not on Stack Overflow? since is didn't involve any programming) I was missing the "belongs on drupal.stackexchange.com" option.

I think an extra option with a select box with all sites out of beta (perhaps minus the options that already have their own radio), could fix this. See this question for a mockup along these lines.

As @lix commented on the question, having all sites enumerated is impractical. But I still think having some pre-guessed options (4?) and a "catch-all" selectbox-option, could work.

Like suggested to More options when flagging for migration, this is growing more and more above the "Don't Make Me Think" barrier and might just not work. A huge select is not any different from a long list of radio-buttons.

One of the related questions I didn't find until @bart pointed them out was answered that moderators already have a great migration UI (see also @fabian's comment or Should some communities have more than 4 migration targets? for a screenshot of the Vote-to-close dialog).

Given all the linked questions I think I'm not the only one confused by the current UI. If an intuitive UI is impossible, we could at least improve the faq, to prevent yet another duplicate post on meta, like this one. The accepted answer to the original feature request Can we have "belongs on some other stackexchange site" as an option when voting to close? is short, yet already clarifying.

11 Migration of MSO links to MSE links
source | link

Possible Duplicate:
More options when flagging for migrationMore options when flagging for migration

When flagging http://stackoverflow.com/questions/9941749/how-to-boost-module-cron-run-or-save as off topic on SO (following http://meta.stackoverflow.com/questions/87719/which-questions-should-be-on-topic-on-drupal-answers-but-not-on-stack-overflowhttp://meta.stackexchange.com/questions/87719/which-questions-should-be-on-topic-on-drupal-answers-but-not-on-stack-overflow since is didn't involve any programming) I was missing the "belongs on drupal.stackexchange.com" option.

I think an extra option with a select box with all sites out of beta (perhaps minus the options that already have their own radio), could fix this. See this questionthis question for a mockup along these lines.

As @lix commented on the question, having all sites enumeratedall sites enumerated is impractical. But I still think having some pre-guessed options (4?) and a "catch-all" selectbox-option, could work.

Like suggested to More options when flagging for migrationMore options when flagging for migration, this is growing more and more above the "Don't Make Me Think" barrier and might just not work. A huge select is not any different from a long list of radio-buttons.

One of the related questions I didn't find until @bart pointed them out was answeredanswered that moderators already have a great migration UI (see also @fabian's comment or http://meta.stackoverflow.com/questions/118685/should-some-communities-have-more-than-4-migration-targetshttp://meta.stackexchange.com/questions/118685/should-some-communities-have-more-than-4-migration-targets for a screenshot of the Vote-to-close dialog).

Given all the linked questions I think I'm not the only one confused by the current UI. If an intuitive UI is impossible, we could at least improve the faq, to prevent yetyet anotheranother duplicate post on meta, like this one. The accepted answeraccepted answer to the original feature request http://meta.stackoverflow.com/questions/48662/can-we-have-belongs-on-some-other-stackexchange-site-as-an-option-when-votinghttp://meta.stackexchange.com/questions/48662/can-we-have-belongs-on-some-other-stackexchange-site-as-an-option-when-voting is short, yet already clarifying.

Possible Duplicate:
More options when flagging for migration

When flagging http://stackoverflow.com/questions/9941749/how-to-boost-module-cron-run-or-save as off topic on SO (following http://meta.stackoverflow.com/questions/87719/which-questions-should-be-on-topic-on-drupal-answers-but-not-on-stack-overflow since is didn't involve any programming) I was missing the "belongs on drupal.stackexchange.com" option.

I think an extra option with a select box with all sites out of beta (perhaps minus the options that already have their own radio), could fix this. See this question for a mockup along these lines.

As @lix commented on the question, having all sites enumerated is impractical. But I still think having some pre-guessed options (4?) and a "catch-all" selectbox-option, could work.

Like suggested to More options when flagging for migration, this is growing more and more above the "Don't Make Me Think" barrier and might just not work. A huge select is not any different from a long list of radio-buttons.

One of the related questions I didn't find until @bart pointed them out was answered that moderators already have a great migration UI (see also @fabian's comment or http://meta.stackoverflow.com/questions/118685/should-some-communities-have-more-than-4-migration-targets for a screenshot of the Vote-to-close dialog).

Given all the linked questions I think I'm not the only one confused by the current UI. If an intuitive UI is impossible, we could at least improve the faq, to prevent yet another duplicate post on meta, like this one. The accepted answer to the original feature request http://meta.stackoverflow.com/questions/48662/can-we-have-belongs-on-some-other-stackexchange-site-as-an-option-when-voting is short, yet already clarifying.

Possible Duplicate:
More options when flagging for migration

When flagging http://stackoverflow.com/questions/9941749/how-to-boost-module-cron-run-or-save as off topic on SO (following http://meta.stackexchange.com/questions/87719/which-questions-should-be-on-topic-on-drupal-answers-but-not-on-stack-overflow since is didn't involve any programming) I was missing the "belongs on drupal.stackexchange.com" option.

I think an extra option with a select box with all sites out of beta (perhaps minus the options that already have their own radio), could fix this. See this question for a mockup along these lines.

As @lix commented on the question, having all sites enumerated is impractical. But I still think having some pre-guessed options (4?) and a "catch-all" selectbox-option, could work.

Like suggested to More options when flagging for migration, this is growing more and more above the "Don't Make Me Think" barrier and might just not work. A huge select is not any different from a long list of radio-buttons.

One of the related questions I didn't find until @bart pointed them out was answered that moderators already have a great migration UI (see also @fabian's comment or http://meta.stackexchange.com/questions/118685/should-some-communities-have-more-than-4-migration-targets for a screenshot of the Vote-to-close dialog).

Given all the linked questions I think I'm not the only one confused by the current UI. If an intuitive UI is impossible, we could at least improve the faq, to prevent yet another duplicate post on meta, like this one. The accepted answer to the original feature request http://meta.stackexchange.com/questions/48662/can-we-have-belongs-on-some-other-stackexchange-site-as-an-option-when-voting is short, yet already clarifying.

10 Linking another related question.
source | link
9 More duplicates
source | link
8 added 261 characters in body
source | link
7 Adding another duplicate.. Can't believe how many there are.. And how I could have missed those all..
source | link
6 re-inserting duplicate link
source | link
5 Bring more structure to the question.
source | link
4 insert duplicate link
source | link
    Post Closed as "exact duplicate" by Lix, yannis, Shadow The Dragon Wizard, Time Traveling Bobby, kiamlaluno of
3 incorporated comments
source | link
2 Following custom moved this from question. Thanks to @lix
source | link
1
source | link