openstack-poc team mailing list archive

[Eric Day <eday@xxxxxxxxxxxx>]

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

On Wed, Apr 13, 2011 at 05:06:23PM -0400, Jay Pipes wrote:
> On Wed, Apr 13, 2011 at 4:09 PM, Vishvananda Ishaya
> <vishvananda@xxxxxxxxx> wrote:
> > New point for the agenda.  We have stuff that needs to go into openstack-common, and we don't really have a PTL for stuff there.  Who manages this?  Authn should be openstack-common for sure.
> 
> Good point. I actually think that openstack-common should *not* have a
> PTL, and that the PTLs for the other projects should propose code
> standards for that project and stuff to go into it. Authn would be a
> great first start, since previous attempts at getting agreement on
> things like option processing and logging didn't get very far.
> 
> John, what do you think?
> 
> -jay
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack-poc
> Post to     : openstack-poc@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack-poc
> More help   : https://help.launchpad.net/ListHelp