The easiest way to accomplish that would be to fork and then do all the necessary transformations (read, file operations and code changes) on such fork. Correct?
Yes, that way will allow easy community integration with your repo based on Numenta’s.
I don’t think we need the python 2.7 code, correct? Full steam ahead, right?
+1 to dropping py2.7
I’m not hard set on this and willing to change back to the original repo structure. For that, I’ll fork from Numenta’s nupic and apply my changes python 3 changes.
++1. That would be awesome. Let’s keep the things a little bit in order, develop your changes on it. And if later it proves beneficial to merge, it’s always possible.
The only question that’s left is where to house my Visual Studio solution. I like to have all code in one solution (read nupic.core and nupic). Should I do a separate repo for that then? I assume a cmake script would then combine the two repo and create a VS solution?
Do you want this as a public endeavor, or just for private use? I’d go with cmake delegating to the two cmakes below. But not sure how you’d handle commits to this merged repo…