Thierry,
Cool thanks for the leeway here ☺
I agree wholeheartedly with your last sentiment. If an existing Kolla sub-team
or an existing project (e.g. the Puppet team) in OpenStack or a new project
wants to use Kolla images and feels they would operate more effectively without
the structure Kolla has in place, I personally as a core reviewer don’t want to
limit that type of activity as long as it fits within the TC’s governance
rules. As a core reviewer, I do want to keep what deliverables we currently
have in place as splitting out deliverables is super disruptive to the Kolla
project. Over 60% of the Ocata cycle has been spent just splitting
kolla-ansible into its own deliverable – meaning we are way behind on
maintenance and development of our existing deliverables. Like all things in
life, my opinion is subject to change in the future.
Regards
-steve
-----Original Message-----
From: Thierry Carrez <thie...@openstack.org>
Organization: OpenStack
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date: Thursday, January 12, 2017 at 6:25 AM
To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [tc][kolla] Adding new deliverables
Michał Jastrzębski wrote:
> So from my point of view, while I understand why project separation
> makes sense in the long run, I will argue that at this moment it will
> be hurtful for the project. Our community is still fairly integrated,
> and I'd love to keep it this way a while longer. We haven't yet fully
> cleaned up mess that split of kolla-ansible caused (documentation and
> whatnot). Having small revolution like that again is something that
> would greatly hinder our ability to deliver valuable project, and I
> think for now that should be our priority.
FWIW my email was not meant as an immediate request to split Kolla
because its internal structure goes against the OpenStack project
structure. In particular as long as the Kolla subteams are fine
operating under a single umbrella and being seen as a single "team",
there is no need to change that, that would be a distraction.
I just wanted to explain that a lot of the organizational problems the
Kolla team is going through are caused by this "umbrella" model and that
we designed the current OpenStack project structure precisely to avoid
them. I also don't want to discourage any Kolla subteam (or future
project leveraging Kolla images) which feels like it would operate
better as a separate project team to file for official inclusion.
Cheers!
--
Thierry Carrez (ttx)
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
