While I'm aiming for general, non-specific solutions, I am using the real example of wanting to re-write my Java logging library
I've recently run into the case where I want to reimplement an existing project in a new language, and I'm trying to decide how best to manage the new code in relation to the existing product.
My initial thoughts were to simply create a new repository; this having the advantage of clear distinctions between project history and issues.
java-repo > master - dir1 - dir2 node-repo > master - dir1 - dir2
I have seen arguments made for keeping all the code in one repository, such as being able to change an algorithm and having all the languages changed in one commit.
project-repo > master - java - dir1 - dir2 - node - dir1 - dir2
The last suggestion I saw was that you could have a 'master' branch for each language, but I think that's a bit too unconventional for my taste...
project-repo > master-java - dir1 - dir2 > master-node - dir1 - dir2
What are your thoughts on this? Is there some hot new methodology that I've missed, or is keeping it old-school with separate repos the way to go?
I might be doing a post about the re-write process at some point, so even if it fails horribly it should at least be interesting! 😄