Skip to main content
6 events
when toggle format what by license comment
May 23, 2017 at 12:36 history edited CommunityBot
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Oct 8, 2015 at 14:43 comment added user213963 I suggest you leave it. Adding additional custom close slots (above the three) for sites could be a way to elevate this issue if the communities of those sites wish to use it as such.
Oct 8, 2015 at 14:35 comment added Rainbolt @MichaelT I didn't understand the difference between "default migration paths" and "the three custom close reasons" until your comment prompted me to do some research. I think now that I posted in the wrong place. Do you have a suggestion for what I should do? I believe there is one small nugget of useful/relevant information in my otherwise mostly off topic answer.
Oct 8, 2015 at 14:20 comment added user213963 ... Consider if you ever got a CodeGolf -> StackOverflow default migration path. You would need to make sure that you aren't migrating the 'homework statement and some broken code' questions there that would get closed for 'not enough information for debugging' on Stack Overflow. Those are the ones that this suggestion targets - to squash rejected migrations from regular users.
Oct 8, 2015 at 14:19 comment added user213963 One challenge that other sites have is that if they've already used their three close reasons on other things, they don't have a spare one for "off topic here, on topic over there, would still get closed for other reasons." Sometimes this gets headed off with a custom close reason (a pain to type), or a 'unclear' as a way to head off people who would otherwise have the tendency to click off topic, other site, stack overflow to punt the question for another site to deal with. This is also chiefly an issue for sites that have migration paths other than to their own meta.
Oct 8, 2015 at 14:15 history answered Rainbolt CC BY-SA 3.0