Update: a blog post based on feedback here and elsewhere:
The history of migration
Stack Exchange has grown considerably over the past few years... When Server Fault first launched, it was an attempt to replicate the formula that had worked so well on Stack Overflow for an audience whose questions... weren't especially welcomed by the majority of programmers. When Super User launched, it was the catch-all anything about computers that isn't about servers or programming site.
Life was simple. Finally, there was a place for everything. And everything could be put in its place: a tool was created to migrate questions asked on Stack Overflow that weren't related to programming to a more welcoming community. At long last, those of us tackling the unpleasant task of turning away good questions simply because they were off-topic could kick off the jackboots and hand these poor folks a welcome basket.
Fast-forward three years...
Forget The Trilogy - Stack Exchange spans 84 sites, covering topics as diverse as gardening and quantitative finance. And forget programming/servers/computery-stuff - there are specialty sites for Drupal coders, CS researchers, and Apple fanboys.
Oh yeah... And then there's DBAs...
Life ain't so simple anymore, eh? Forget about a place for everything; there might be three places for everything. Or a dozen. Shucks... I know someone out there right now is trying to compose a question that can be copied, verbatim, to every site on the network without being inappropriate on any of them.
And DBAs is one of a growing handful of sites where literally everything that can be reasonably asked was already on-topic somewhere else first.
The reasons why scope overlaps
This has created a bit of confusion... Especially with regard to how the Migrate tool should be used. So I think it's worth pointing out a couple of facts:
Sites are created based on audience, not topic. This is key to understanding why overlapping scopes are allowed at all: CMS users aren't limited to programmers, DBAs aren't just server admins and SQL coders. When a field of expertise isn't wholly contained by the audience of an existing site, there's room for the establishment of another that better represents it.
Migration is intended to help users who don't realize their question is off-topic, not enforce some abstract organizational scheme. Just because a topic can be on-topic in multiple places doesn't mean it must be tossed around like a hot potato until someone finally gets stuck with it.
None of this is new; even in the original trilogy, there were some who found the divisions arbitrary, and questioned the need for three separate sites. Jeff wrote about the idea of a site as a gathering place for domain experts back in '09:
Is it really so hard to figure out which community you belong to, and thus, where your question belongs? Ask yourself this:
- what is your job title?
- which community do you consider yourself a part of?
- what are you trying to accomplish?
You can use the same mountain to go downhill really fast on snow — but it’s plainly evident to the participant which culture they consider themselves a part of, “skiers” or “snowboarders”.
That's why this site is named Database Administrators and not, say, "Databases". Without first defining who you are, there's no good way to determine who should be asking questions here. The absence of some other language, or the perceived "difficulty level" of a question are poor metrics for determining the ideal place to ask - the second question isn't "what are you asking", but "who do you want to ask"? Topic comes into play last...
Be jealous of your own site
As members of a community, your loyalty should be first to your community. When evaluating a question, you shouldn't be looking for somewhere else to dump it, but rather asking if it could possibly be appropriate and on-topic for you, the experts who the author decided to ask. Be a bit jealous of your community - don't blithely turn askers away simply because their question could be asked somewhere else.
Obviously, there are questions you'll have to turn away, either because their only connection to your site is via the audience ("How do I make bread as a programmer?") or because they're simply poorly-asked. But that should be your last resort. Close with an eye toward improvement and re-opening, not voting users off the island.
Welcome questions from other sites... But don't drag them in kicking and screaming
Along the same lines, don't attempt to "scavenge" on-topic questions from other sites by asking the moderators there to migrate them to yours. I've encountered entirely too much frustration from users on both Stack Overflow and Server Fault who've seen questions snatched away, their authors left confused as to what they did wrong... This is the opposite of what migration was intended to do! It's one thing to suggest in a comment that a question might be better answered somewhere else, or flag one already closed as off-topic, but migrating a question from a user who thought - and rightly so - that he was in the right place just because he could also have been right in another place... Is a rude slap in the face, and a disservice to both sites.
Finally, be extremely reluctant to migrate old, answered, popular questions, especially from older sites to newer ones. The votes and answers on these reflect the opinions and work of their specific community, and in most cases will be somewhat out of place elsewhere. And again, the migration can come across as rude - if someone has invested serious effort into an answer on Stack Overflow, linked to it on their blog or from their résumé, snatching it from them without due consideration won't endear them to you.
The other users of your sites depend on you - all of you - to behave responsibly with the tools you've been given. Please focus on them, the actual humans who make up these communities, and not some arbitrary definition of scope.