Open Stack

On Fri, Sep 20, 2013 at 3:20 PM, Monty Taylor <mordred at inaugust.com> wrote:

>
> What if we rethought the organization just a little bit. Instead of
> having oslo-incubator from which we copy code, and then oslo.* that we
> consume as libraries, what if:
>
> - we split all oslo modules into their own repos from the start
> - we make update.py a utility that groks copying from a directory that
> contains a bunch of repos - so that a person wanting to use is might have:
>   ~/src
>   ~/src/oslo
>   ~/src/oslo/oslo.db
>   ~/src/oslo/oslo.policy
>   and then when they run update.py ~/src/oslo ~/src/nova and get the
> same results (the copying and name changing and whatnot)
>
>
I like this structure a little more than the current structure.  It feels
more like python modules.

If the bonus is to also allow more granularity on reviewing (e.g.
per-module cores), I think that there is another win to be had there.


> That way, we can add per-module additional core easily like we can for
> released oslo modules (like hacking and pbr have now)
>
> Also, that would mean that moving from copying to releasing is more a
> matter of just making a release than it is of doing the git magic to
> split the repo out into a separate one and then adding the new repo to
> gerrit.
>
>
I like this approach.  It does make the barrier to go from copy->release a
bit lower.  Less barrier is better (not that everything will go that route
immediately).

 Thoughts?
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

--Morgan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130920/a0118f74/attachment.html>