Skip to main content
Commonmark migration
Source Link

This was brought up on Meta Stack Exchange a few years back. The main reasoning for not adding more was:

Adding even more migration paths to this existing close list would clutter the UI. The idea is to show the most frequent migration paths so the users to can migrate most questions.

Along with a variety of other reasons that were brought up. Here's a few more:

Unless you are very familiar with the community that will be receiving the question, you should not be migrating it there. Moderators can get in touch with other moderators on the receiving site when in doubt.

 

Questions not in the given paths to migrate should not be migrated unless there is a compelling reason to do so. The end result of a migration is ensuring that a question gets more high quality answers faster than it would otherwise.

This was brought up on Meta Stack Exchange a few years back. The main reasoning for not adding more was:

Adding even more migration paths to this existing close list would clutter the UI. The idea is to show the most frequent migration paths so the users to can migrate most questions.

Along with a variety of other reasons that were brought up. Here's a few more:

Unless you are very familiar with the community that will be receiving the question, you should not be migrating it there. Moderators can get in touch with other moderators on the receiving site when in doubt.

 

Questions not in the given paths to migrate should not be migrated unless there is a compelling reason to do so. The end result of a migration is ensuring that a question gets more high quality answers faster than it would otherwise.

This was brought up on Meta Stack Exchange a few years back. The main reasoning for not adding more was:

Adding even more migration paths to this existing close list would clutter the UI. The idea is to show the most frequent migration paths so the users to can migrate most questions.

Along with a variety of other reasons that were brought up. Here's a few more:

Unless you are very familiar with the community that will be receiving the question, you should not be migrating it there. Moderators can get in touch with other moderators on the receiving site when in doubt.

Questions not in the given paths to migrate should not be migrated unless there is a compelling reason to do so. The end result of a migration is ensuring that a question gets more high quality answers faster than it would otherwise.

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

This was brought upbrought up on Meta Stack Exchange a few years back. The main reasoning for not adding more was:

Adding even more migration paths to this existing close list would clutter the UI. The idea is to show the most frequent migration paths so the users to can migrate most questions.

Along with a variety of other reasons that were brought up. Here's a few more:

Unless you are very familiar with the community that will be receiving the question, you should not be migrating it there. Moderators can get in touch with other moderators on the receiving site when in doubt.

Questions not in the given paths to migrate should not be migrated unless there is a compelling reason to do so. The end result of a migration is ensuring that a question gets more high quality answers faster than it would otherwise.

This was brought up on Meta Stack Exchange a few years back. The main reasoning for not adding more was:

Adding even more migration paths to this existing close list would clutter the UI. The idea is to show the most frequent migration paths so the users to can migrate most questions.

Along with a variety of other reasons that were brought up. Here's a few more:

Unless you are very familiar with the community that will be receiving the question, you should not be migrating it there. Moderators can get in touch with other moderators on the receiving site when in doubt.

Questions not in the given paths to migrate should not be migrated unless there is a compelling reason to do so. The end result of a migration is ensuring that a question gets more high quality answers faster than it would otherwise.

This was brought up on Meta Stack Exchange a few years back. The main reasoning for not adding more was:

Adding even more migration paths to this existing close list would clutter the UI. The idea is to show the most frequent migration paths so the users to can migrate most questions.

Along with a variety of other reasons that were brought up. Here's a few more:

Unless you are very familiar with the community that will be receiving the question, you should not be migrating it there. Moderators can get in touch with other moderators on the receiving site when in doubt.

Questions not in the given paths to migrate should not be migrated unless there is a compelling reason to do so. The end result of a migration is ensuring that a question gets more high quality answers faster than it would otherwise.

Source Link
Simon Sheehan
  • 9.2k
  • 23
  • 35

This was brought up on Meta Stack Exchange a few years back. The main reasoning for not adding more was:

Adding even more migration paths to this existing close list would clutter the UI. The idea is to show the most frequent migration paths so the users to can migrate most questions.

Along with a variety of other reasons that were brought up. Here's a few more:

Unless you are very familiar with the community that will be receiving the question, you should not be migrating it there. Moderators can get in touch with other moderators on the receiving site when in doubt.

Questions not in the given paths to migrate should not be migrated unless there is a compelling reason to do so. The end result of a migration is ensuring that a question gets more high quality answers faster than it would otherwise.