Usually on a software project in Github, developers fork nupic once, and everyone has their own local forked copy. PRs are created from the forks and compared to master, and must be approved before merging. We are not actively developing NuPIC or nupic.core at the moment. They are both in maintenance mode. All our engineers are researching, not writing production code. So we don’t have the engineers to process the large code changes required for an endeavor like updating to python 3.
So the alternative is a community fork. Any fork of NuPIC could diverge from master at any time. So when I say community fork I mean one that is maintained by the community and diverges from master.
Because our repos are in maintenance mode, we don’t expect it to change very often, so keeping these divergent forks up to date with master probably won’t be hard. But if there is going to be a community fork, someone should be in charge of merges and keeping it up to date with master (if that is favorable).