-10

I recently came over this question where the decision to migrate it from SE Electrical Engineering to SE Code Review was obviously wrong, as that question doesn't fit for the target site policies.

I don't know how moderators communicate over cross site boundaries, but I'm sure that such migration action should be reviewed and confirmed by the target site moderators and go there in first place.

  • 1
    I would expect the general don't migrate crap would apply here. I'm not sure if we need a feature / process for something that is probably a missclick. Maybe ping the mod: electronics.stackexchange.com/posts/359501/timeline – rene Mar 3 '18 at 18:10
  • @rene If there's such policy already (and crap actually applies there IMO), I'm just fine with it. The mod was pinged already by me, but the comment is removed now. – πάντα ῥεῖ Mar 3 '18 at 18:13
  • I think push-pull of questions between communities' review queues could work: meta.stackexchange.com/a/186461/215590 – PolyGeo Mar 3 '18 at 19:36
14

Actually, the standard recommendation to the moderators (from the CMs) is specifically to not ask a site mod before migrating:

You don't need permission to migrate questions, and definitely shouldn't be pinging moderators on another site every time you have something that needs migration.

While mods are an easy source of knowledge about a site, they're not the all-knowing, final deciders of site scope; the users are. As such, rejecting the migration can be done by any five users closing the question for any reason (duplicates will stay but be marked as duplicates). There's really no reason to get another moderator involved. Shog explains the process for migration here.

That said, like with any migration, the rule for moderators and regular users alike is "Don't migrate crap" and we generally hope that our fellow mods will at least look at the site guidance before migrating, particularly when trying to send something to a site they're unfamiliar with... but it's really not a big deal. But, if a question looks on topic and doesn't look like a horrible question, there's no real reason to wait on migrating it to get a response from a site mod on the target site.

Occasionally I've seen (and have done myself) that mods on a site will come and report in to the migrating moderator to let them know if a the question was a bad fit for the site, particularly when several questions were migrated that were bad fits... but clearing every migration before sending is unnecessary.

5

Just close and/or delete the question, or if you're not a mod/high rep user flag the post with the "other" option explaining the problem. That'll reject the migration.

If it keeps happening then the site mods can ping the other site's mods in TL to remind them to be careful when migrating that a) the question isn't just a bad question and b) it's actually on topic on the target site.

All mods should take the view that if there's any doubt about a migration then don't do it.

  • I'm of too low rep there (SECR) to propose deletion, otherwise I would have done so be sure. – πάντα ῥεῖ Mar 3 '18 at 18:17
  • @πάνταῥεῖ - ah. I assumed you were a mod/high rep user - sorry. In that case flag the post using the "other" option. One of the mods will do the needful. – ChrisF Mar 3 '18 at 18:18
  • "In that case flag the post ..." That's what I did of course. But such mistakes should be prevented beforehand IMO, that's why I put this FR. – πάντα ῥεῖ Mar 3 '18 at 18:21

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .