Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Can we move questions?
This question was accidentally posted in meta instead of language, and ended up being closed. Does the ability to move questions between sites currently exist, or is closing the only way to deal with it right now?
2 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
I don't think we should have this feature. In my (limited) experience at Stack Exchange, when people suggest moves to other sites they, by and large, do not know the proposed recipient site's mores and topics to know whether the post would be wanted there. And even when it a certain question would indeed be appropriate on another site, which is a small minority of off-topic closures, there's no great loss in not moving it thither: one can always inform the asker that, though the question was closed as off-topic, it's topical at site X and he should ask it there. I think the false positives, proposed false positives, time spent reviewing proposed moves, arguments, etc. are not worth the small benefit in having this feature.
I have raised this discussion in the past, particularly in the context of "one database per community" vs. "one database per instance". We are currently in "one database per instance", where moving a question between communities ("migrate" in SE terminology) would really be only very slightly more complex than moving between categories. However:
- There is general consensus that long-term we should be in "one database per community" in order to handle high loads better (and other reasons). A migration in that setup will be more complex, so building it now "easy" would result in a feature that would require some serious (though not insurmountable) work later.
- Until we have a high volume of questions (at which point, we may really want to have the multiple databases), the need to migrate will be relatively minimal. I could see, for example, an "outdoors photography" question being migrated from outdoors to photography. But we don't have, for example, the issue of migration between a general programming site and specific computer languages, or between linguistics and specific human languages, or woodworking to DIY, etc. simply because we don't have most of these communities (yet).
So it is a feature I'd like to see, but, despite my original thoughts on the matter several months ago, not something I think we need any time soon.
0 comment threads
1 comment thread