Return to Answer

This is a good question asked on the wrong site.

Because it has no code and no tie in to specific software or even a language, it's really a software architecture/algorithm design question and is suitable for Programmers or Computer Science. Partly because it's obviously so popular tasty we really should go to the extra trouble of making it a good example for the rest of the network instead of a bad one.

Ideally it should have been migrated there within minutes and none of this would be an issue. Unfortunately it wasn't caught and how it's turned into a bike-shed question. This is a good example of why migrating questions should reset votes. This should be handled automatically by the close system. Since it's not, something has to give.

Option 1: Just migrate it already.

Drawbacks are that votes are going to be reflective of a different community and a few answers will be out of place. Bummer. Fix the migrate system.

If that's an unacceptable result...

Option 2: Manually twiddle everything to pseudo-migrate.

The drawback is quite a bit of hassle and consternation, but in the end everybody lives happily ever after.

1. Close the current question
2. Ask the OP to copy/paste it to a new question on Programmers
3. Link everybody to the new question, creating new answers.
4. Lock the old one so votes/comments don't collect on both.

In the end everybody that put work into writing questions and answers will get even MORE rep out of the deal for their troubles, but the resulting question will be on the community where the question best fits and is most suited to vote on it's merits.

This is a good question asked on the wrong site.

Because it has no code and no tie in to specific software or even a language, it's really a software architecture/algorithm design question and is suitable for Programmers or Computer Science. Partly because it's obviously so popular tasty we really should go to the extra trouble of making it a good example for the rest of the network instead of a bad one.

Ideally it should have been migrated there within minutes and none of this would be an issue. Unfortunately it wasn't caught and how it's turned into a bike-shed question. This is a good example of why migrating questions should reset votes. This should be handled automatically by the close system. Since it's not, something has to give.

Option 1: Just migrate it already.

Drawbacks are that votes are going to be reflective of a different community and a few answers will be out of place. Bummer. Fix the migrate system.

If that's an unacceptable result...

Option 2: Manually twiddle everything to pseudo-migrate.

The drawback is quite a bit of hassle and consternation, but in the end everybody lives happily ever after.

1. Close the current question
2. Ask the OP to copy/paste it to a new question on Programmers
3. Link everybody to the new question, creating new answers.
4. Lock the old one so votes/comments don't collect on both.

In the end everybody that put work into writing questions and answers will get even MORE rep out of the deal for their troubles, but the resulting question will be on the community where the question best fits and is most suited to vote on it's merits.

This is a good question asked on the wrong site.

Because it has no code and no tie in to specific software or even a language, it's really a software architecture/algorithm design question and is suitable for Programmers or Computer Science. Partly because it's obviously so popular tasty we really should go to the extra trouble of making it a good example for the rest of the network instead of a bad one.

Ideally it should have been migrated there within minutes and none of this would be an issue. Unfortunately it wasn't caught and how it's turned into a bike-shed question. This is a good example of why migrating questions should reset votes. This should be handled automatically by the close system. Since it's not, something has to give.

Option 1: Just migrate it already.

Drawbacks are that votes are going to be reflective of a different community and a few answers will be out of place. Bummer. Fix the migrate system.

If that's an unacceptable result...

Option 2: Manually twiddle everything to pseudo-migrate.

The drawback is quite a bit of hassle and consternation, but in the end everybody lives happily ever after.

1. Close the current question
2. Ask the OP to copy/paste it to a new question on Programmers
3. Link everybody to the new question, creating new answers.
4. Lock the old one so votes/comments don't collect on both.

In the end everybody that put work into writing questions and answers will get even MORE rep out of the deal for their troubles, but the resulting question will be on the community where the question best fits and is most suited to vote on it's merits.

This is a good question asked on the wrong site.

Because it has no code and no tie in to specific software or even a language, it's really a software architecture/algorithm design question and is suitable for Programmers or Computer Science. Partly because it's obviously so popular tasty we really should go to the extra trouble of making it a good example for the rest of the network instead of a bad one.

Ideally it should have been migrated there within minutes and none of this would be an issue. Unfortunately it wasn't caught and how it's turned into a bike-shed question. This is a good example of why migrating questions should reset votes. This should be handled automatically by the close system. Since it's not, something has to give.

Option 1: Just migrate it already.

Drawbacks are that votes are going to be reflective of a different community and a few answers will be out of place. Bummer. Fix the migrate system.

If that's an unacceptable result...

Option 2: Manually twiddle everything to pseudo-migrate.

The drawback is quite a bit of hassle and consternation, but in the end everybody lives happily ever after.

1. Close the current question
2. Ask the OP to copy/paste it to a new question on Programmers
3. Link everybody to the new question, creating new answers.
4. Lock the old one so votes/comments don't collect on both.

In the end everybody that put work into writing questions and answers will get even MORE rep out of the deal for their troubles, but the resulting question will be on the community where the question best fits and is most suited to vote on it's merits.

This is a good question asked on the wrong site.

Because it has no code and no tie in to specific software or even a language, it's really a software architecture/algorithm design question and is suitable for Programmers or Computer Science. Partly because it's obviously so popular tasty we really should go to the extra trouble of making it a good example for the rest of the network instead of a bad one.

Ideally it should have been migrated there within minutes and none of this would be an issue. Unfortunately it wasn't caught and how it's turned into a bike-shed question. This is a good example of why migrating questions should reset votes. This should be handled automatically by the close system. Since it's not, something has to give.

Option 1: Just migrate it already.

Drawbacks are that votes are going to be reflective of a different community and a few answers will be out of place. Bummer. Fix the migrate system.

If that's an unacceptable result...

Option 2: Manually twiddle everything to pseudo-migrate.

The drawback is quite a bit of hassle and consternation, but in the end everybody lives happily ever after.

1. Close the current question
2. Ask the OP to copy/paste it to a new question on Programmers
3. Link everybody to the new question, creating new answers.
4. Lock the old one so votes/comments don't collect on both.

In the end everybody that put work into writing questions and answers will get even MORE rep out of the deal for their troubles, but the resulting question will be on the community where the question best fits and is most suited to vote on it's merits.

This is a good question asked on the wrong site.

Because it has no code and no tie in to specific software or even a language, it's really a software architecture/algorithm design question and is suitable for Programmers or Computer Science. Partly because it's obviously so popular tasty we really should go to the extra trouble of making it a good example for the rest of the network instead of a bad one.

Ideally it should have been migrated there within minutes and none of this would be an issue. Unfortunately it wasn't caught and how it's turned into a bike-shed question. This is a good example of why migrating questions should reset votes. This should be handled automatically by the close system. Since it's not, something has to give.

Option 1: Just migrate it already.

Drawbacks are that votes are going to be reflective of a different community and a few answers will be out of place. Bummer. Fix the migrate system.

If that's an unacceptable result...

Option 2: Manually twiddle everything to pseudo-migrate.

The drawback is quite a bit of hassle and consternation, but in the end everybody lives happily ever after.

1. Close the current question
2. Ask the OP to copy/paste it to a new question on Programmers
3. Link everybody to the new question, creating new answers.
4. Lock the old one so votes/comments don't collect on both.

In the end everybody that put work into writing questions and answers will get even MORE rep out of the deal for their troubles, but the resulting question will be on the community where the question best fits and is most suited to vote on it's merits.