If the other team lets you do the work, who's going to review it, explain the codebase to you and, by FAR the most important thing: who's going to maintain it w

If the other team lets you do the work, who's going to review it, explain the codebase to you and, by FAR the most important thing: who's going to maintain it when it breaks? Are you commiting your team and your time to a response when a bug appears with your code or when it needs to be migrated? That's pretty much the same issue as FOSS maintainers have with random drive-by patches - someone needs to still maintain that stuff in the future and in 99% the original owner fscks off by that time leaving the original team to deal with their artsy hacky creation.