<html><body>
<p><tt><font size="2">Thierry Carrez <thierry@openstack.org> wrote on 08/07/2014 06:23:56 AM:<br>
<br>
> From: Thierry Carrez <thierry@openstack.org></font></tt><br>
<tt><font size="2">> To: openstack-dev@lists.openstack.org</font></tt><br>
<tt><font size="2">> Date: 08/07/2014 06:25 AM</font></tt><br>
<tt><font size="2">> Subject: Re: [openstack-dev] Fwd: FW: [Neutron] Group Based Policy <br>
> and the way forward</font></tt><br>
<tt><font size="2">> <br>
> Armando M. wrote:<br>
> > This thread is moving so fast I can't keep up!<br>
> > <br>
> > The fact that troubles me is that I am unable to grasp how we move<br>
> > forward, which was the point of this thread to start with. It seems we<br>
> > have 2 options:<br>
> > <br>
> > - We make GBP to merge as is, in the Neutron tree, with some minor<br>
> > revision (e.g. naming?);<br>
> > - We make GBP a stackforge project, that integrates with Neutron in some<br>
> > shape or form;<br>
> > <br>
> > Another option, might be something in between, where GBP is in tree, but<br>
> > in some sort of experimental staging area (even though I am not sure how<br>
> > well baked this idea is).<br>
> > <br>
> > Now, as a community we all need make a decision; arguing about the fact<br>
> > that the blueprint was approved is pointless.</font></tt><br>
<tt><font size="2">> I agree with you: it is possible to change your mind on a topic and<br>
> revisit past decisions. </font></tt><br>
<tt><font size="2">> In past OpenStack history we did revert merged<br>
> commits and remove existing functionality because we felt it wasn't that<br>
> much of a great idea after all. Here we are talking about making the<br>
> right decision *before* the final merging and shipping into a release,<br>
> which is kind of an improvement. The spec system was supposed to help<br>
> limit such cases, but it's not bullet-proof.<br>
> <br>
> In the end, if there is no consensus on that question within the Neutron<br>
> project (and I hear both sides have good arguments), our governance<br>
> gives the elected Neutron PTL the power to make the final call. If the<br>
> disagreement is between projects (like if Nova disagreed with the<br>
> Neutron decision), then the issue could be escalated to the TC.<br>
> </font></tt><br>
<br>
<tt><font size="2">It is good to know that the OpenStack governance provides a way to resolve these issues but I really hope that we can reach a consensus. </font></tt><br>
<br>
<tt><font size="2">Best,</font></tt><br>
<br>
<tt><font size="2">Mohammad</font></tt><br>
<br>
<br>
<tt><font size="2"><br>
> Regards,<br>
> <br>
> -- <br>
> Thierry Carrez (ttx)<br>
> <br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> OpenStack-dev@lists.openstack.org<br>
> </font></tt><tt><font size="2"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></font></tt><tt><font size="2"><br>
> <br>
</font></tt></body></html>