@Romulus the NEO code will be generally available once we start versioning it. The main reason we're not opening the repository now is our current DevOps setup. We are developing NEO as a reference app with multiple components and a set of default settings. Then each client instance is a branch that syncs default files and adds custom configuration files specific to each branch. There are strict rules to which files you can and can not edit to ensure that your branch can continue to sync. It is also important to ensure that the backend (UNA) is configured correctly.

So, we need to provide documentation to ensure you can in fact setup and sync NEO. With a few commits happening every day it's not going to be very useful as a "starter" unless you can update it easily and frequently.

With that said, we are already testing the full Spacenook Kit (UNA + NEO) and now setting up the preconfigured Core Kit (for the basic UNA Core + NEO combination). So, not too far now. Most of the time allocated to delivery of those kits is after we release 3 client projects we are working on now.