(thought I posted this in response to Mike, but just seeing now that I didn't... )
Since it is going to be a completely new code base, doesn't it make sense to start a new repo? I guess from a naming convention it does make it easier. Is there any kind of best practice around this type of situation?
That being said, if the general consensus is to use the same repo, I'm fine with that...