Whether you want to build the software, run it, grow the community or just learn more about it, there will be content, workshops and design sessions for you to attend at the OpenStack Summit, Oct 15-18 in San Diego. Stick around Friday for the first OpenStack service day, a 1/2 day beach cleanup.
The nova project should be broken up further. cinder + common was a good first step, let's go further.
I think it would be a good idea to have seperate Modules (which will be represented by own git repos, python or distro packages...) for things that are mutually exlusive (e.g. when I use the hyper-v hypervisor I will not be using Xen on the same node, so these should be different modules).
I can see the following things to be broken out: - nova objectstore - nova certs - nova keys - nova hypervisor xen - nova hypervisor kvm - nova hypervisor vmware - nova hypervisor hyper-v - nova networking "classic" - nova networking quantum - nova cloudpipe - nova compute - nova scheduler filter - nova scheduler etc.
This will also lead to the need to define the APIs between the modules better which I think is a plus (e.g. what exactly will the hypervisor API look like? Which method calls with what kind of params etc.)
One of the objections might be "but all the dependencies". Yes. This is a challenge, but this should be addressed as well. Sane pip-require files should do that.