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.
How do we handle overlap?
When I use SO I see a load of questions that would be better asked on a spin-off site. Eg SQL questions that would be way better answered on DBA.se.
But SQL is a programming language and so fits on SO as well.
It's a situation that would only ever be resolved if any question on any site could be referenced and shown on any other site "simultaneously".
So a simple suggestion would be to allow posts to be sent to a different site where they would appear as native questions. Anyone clicking then would be taken to the originating site (but it'd be cool if they could appear in-situ, embedded in the target site)
There is a community aspect to this that can be lost if we just think of questions as being things that fit into buckets …
4y ago
There are two sides to this question Questions that are on-topic on more than one site There were three principle …
4y ago
Migrating questions between sites never worked well in practice. We have a lot of experience about this from SE's variou …
4y ago
I have to agree, migrating posts was a mess. But a solution of closing and making the poster cut and paste his questi …
4y ago
4 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.
There are two sides to this question
Questions that are on-topic on more than one site
There were three principle I followed on Stack Exchange for questions that would be at home on more than one site
-
They may be asked on either site.
This does lead to duplicates on the network which is moderately annoying. I would generally leave a comment if I know of a cross-site duplicate.
-
Should not be asked "simultaneously" on more than one site.
Where the time frame after which it is reasonable to re-ask on another site depends on the activity of the hosting site. A day or two for a moderate activity site like physics.se, longer on lower activity sites.
-
Let the user know if there is a more specialized site by leaving a comment on the lines of "This is on-topic here, but you might find a more concentrated audience on [specialists-site]".
Questions asked on the wrong site
In my opinion migration worked worse on Stack Overflow than in much of the rest of the network. Which is not to say that it ran really cleanly elsewhere, but for other sites it would be too strong to say it "never worked" or even "rarely worked". Partially a scale thing, I'm sure.
The single biggest problem I saw with user votes to migrate from physics was users not really understanding what was on-topic on the target site. At the moderator level we used to ping the mods on the other site in the Teacher's Lounge for a sanity check, but that doesn't scale. We need a mechanism to (attempt to) insure that anyone casting such a vote knows what they are doing and cares about getting it right.
Proposal: Voting to migrate has a rep/trust threshold on both the originating site and the target site.
0 comment threads
There is a community aspect to this that can be lost if we just think of questions as being things that fit into buckets (sites). A user might choose to ask a question on the "general" site instead of the specialized one because the person is part of the community on the "general" site. It's pretty frustrating (speaking from experience) when your question that is on-topic here gets migrated away to someplace else where you're not. So even if there is a "better" place for a question based on site scopes, if it's on-topic where it was asked it should be left alone. It's fine to let the author know about the other site, particularly if it's a new user who isn't invested in either, but we should let the person with the question decide where to ask it (among on-topic options).
Yes, that means some SQL questions will be on the programming site and some will be on the databases site. We should look for ways to make cross-site related questions/tags visible on both ends. We might even think in terms of showing siteA:tagX questions on siteB where tagX is also interesting. This is an idea for future consideration, not a baked proposal.
If a question is on-topic on more than one site and is tuned for each site, I don't have a problem with it being asked on both sites. An author who does this should link the questions together so everybody who finds one part of it also finds a trail to the other parts.
For now I think of overlap and cross-site duplicates or partial duplicates as a human issue, not a technical one. Migration on SE never worked well from either the human or technical perspective; let's figure out how to do better.
Migrating questions between sites never worked well in practice. We have a lot of experience about this from SE's various experiments: there was rarely ever a successfully migrated post but countless fiascos. The OP got confused, the users of the target site got annoyed, moderators got pointless busy-work and then got yelled at for doing it wrong.
The sober way to deal with such questions is to close them as off-topic, then give the OP a nudge towards the other site where the question might on-topic. Preferably towards the other site's "what's on-topic here" page, since the OP already failed to read that one for the current site.
0 comment threads
I have to agree, migrating posts was a mess.
But a solution of closing and making the poster cut and paste his question on a different site is the exact same process, just more difficult.
1 comment thread