On Apr 13, 2011, at 7:07 PM, Eric Day wrote: > I'm starting to think that openstack-common may be bad approach for > some of the things we've been talking about sticking in there. Instead, > we may want to create other projects such as openstack-auth, > openstack-logging, etc. If we start shoving things all into one > package, it may be harder to break things out later. > > I think this will also make it easier to assign PTLs to specific > projects, since the openstack-auth PTL probably won't want to also > focus on openstack-logging. > > I think there may still be a place for openstack-common for things > like dynamic class import handling, process wrappers, config/option > processing, etc, and this should most likely be driving by the other > project PTLs. > > -Eric
I had a long email typed out, but it really comes down to the following question for me: "Is openstack-common a place for smaller, independent components of an openstack deploy that can be shared by the larger projects, or is it a common library that the projects make user of in their respective code?" Answering this, as a part of establishing guidelines for what's in openstack-common, will help us answer these questions. --John
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Mailing list: https://launchpad.net/~openstack-poc Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
