On 20/06/18 12:38, HADDLETON, Robert W (Bob) wrote:
The Tacker team is dependent on tosca-parser and heat-translator but
they are not the only consumers.
I agree the structure is odd, and Sahdev has more of the history than I do.
History lesson:
At the time (2014) OpenStack was organised into 'Programs', that could
contain multiple projects. It seemed to make sense to bring
heat-translator into the Orchestration Program. It had its own PTL
(Sahdev) and its own core team (although Heat cores from the time still
have +2 rights on it), and operated essentially independently.
There were discussions about eventually combining it with heatclient or
even Heat itself once it was mature, but that hasn't come up in quite a
while and there are no resources available to work on it now anyway.
When we scrapped 'Programs', it just got converted to a deliverable of
the Heat project, instead of its own separate project. In practice,
however, nothing actually changed and it kept its own (technically
unofficial, I think) PTL and operated independently. That's the source
of the weirdness.
Since then the number of core reviewers has dropped considerably and
people have difficulty getting patches in and releases made. Most of the
people bugging me about that have been from Tacker, hence the suggestion
to move the project over there: since they are the biggest users they
could help maintain it.
In the past the requests from the Tacker team have come to Sahdev/me and
we have created
releases as needed. For some reason this time a request went to the
Heat ML, in addition to
a separate request to me directly.
I'm open to changes in the structure but I don't think Tacker is the
right place to put the
deliverables.
What would you suggest?
cheers,
Zane.
Bob
On 6/20/2018 11:31 AM, Rico Lin wrote:
To continue the discussion in
http://lists.openstack.org/pipermail/openstack-dev/2018-June/131681.html
Add Tacker and heat-translator to make sure all aware this discussion
On Thu, Jun 21, 2018 at 12:28 AM Doug Hellmann <d...@doughellmann.com
<mailto:d...@doughellmann.com>> wrote:
Excerpts from Zane Bitter's message of 2018-06-20 12:07:49 -0400:
> On 20/06/18 11:40, Rico Lin wrote:
> > I send a release patch now
https://review.openstack.org/#/c/576895/
> > Also, add Bob Haddleton to this ML who is considering as PTL for
> > heat-translator team
>
> Is it time to consider moving the heat-translator and
tosca-parser repos
> from being deliverables of Heat to deliverables of Tacker? The
current
> weird structure dates from the days of the experiment with
OpenStack
> 'Programs' (vs. Projects).
>
> Heat cores don't really have time to be engaging with
heat-translator,
> and Tacker is clearly the major user and the thing that keeps
getting
> blocked on needing patches merged and releases made.
It sounds like it. I had no idea there was any reason to look to
anyone
other than the Heat PTL or liaison for approval of that release. A WIP
on the patch would have been OK, too, but if the Tacker team is really
the one responsible we should update the repo governance.
Doug
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
May The Force of OpenStack Be With You,
*/Rico Lin
/*irc: ricolin
__________________________________________________________________________
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