The main issue I have with migrated posts is that they can't be closed and then edited (the migration gets rejected and they get sent back). To prevent this unfortunate occurrence, I would suggest:
- If someone on Programmers understands TWP, they should edit it prior to migration
- If nobody on Programmers understands TWP, they should ask in the Water Cooler for someone to edit it (and be around to approve the edit)
- If nobody is around in the Water Cooler, they should use best judgment
For instance, this question could have been edited to change it from, "Can they do that?" to "How can I negotiate to avoid that?" This question would have been a good fit if it were changed from, "How many hours do you guys log?" to "How do you handle non-work hours like lunches or meetings when allotting manpower?" or something of the like.
Since there is a lack of community consensus on when and how to edit, these questions have a higher chance to become missed opportunities if they get closed after being migrated (yes, I know we can flag you and you can unilaterally revoke the lock). A far better approach is to edit them prior to coming over, so that they get received well -- it will also get users more interested in our community if they see what our community standards are and aren't welcomed by downvotes and/or close votes.
Ideally whoever migrates the post can do the edit on the Programmer's side. If not, they should come to The Water Cooler and ask if someone can do it. If there isn't anyone around and they are impatient, they should use their best judgment.