<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 21 October 2015 at 09:52, Gal Sagie <span dir="ltr"><<a href="mailto:gal.sagie@gmail.com" target="_blank">gal.sagie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Wed, Oct 21, 2015 at 7:37 PM, Armando M. <span dir="ltr"><<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On 21 October 2015 at 04:12, Gal Sagie <span dir="ltr"><<a href="mailto:gal.sagie@gmail.com" target="_blank">gal.sagie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div>Do we also want to consider Project Kuryr part of this?<br></div></div></div></div></blockquote><div><br></div></span><div>No, why would we?</div></div></div></div></blockquote><div><br></div></span><div>[Gal] Because Kuryr is a special project which was created in order to expose Neutron and its services to containers networking, </div><div> its mission (at least as defined right now) is to bridge the gaps between containers networking world and Neutron and for doing it</div><div> it already depends on the feature/spec process of Neutron.</div><div> That is why it make sense to me that just like the services projects, our spec approval process will be handled</div><div> as part of Neutron. </div></div></div></div></blockquote><div><br></div><div>Kuryr is no more special than any other Neutron affiliated project, let's be 100% clear about that: there is no double-standard here.</div><div><br></div><div>If you really think that Kuryr should be an integral part of the Neutron project, then it should not exist, but fold within Neutron entirely. I don't know the backstory of why this was spun off as a separate project in the first place, but I think that there's some merits in having it as standalone entity.</div><div><br></div><div>You are always welcome to reach out for feedback, after all the same people may work/have an interest in multiple projects (fingers stuck in many pies if you will :P), but going from there to what you're proposing is too big of a leap which I find hard to justify.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> </div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div></div>We already started sending Kuryr spec to the Neutron repository and I think it would make sense to manage it<br></div>as part of Neutron spec process.<br></div></div></blockquote><div><br></div></span><div>No, unless what you are asking are changes to the core. Do you have a reference for me to look at?</div><div><div><div> </div></div></div></div></div></div></blockquote></span><div> [Gal] I dont understand what you mean "No" here, first this spec is sent to Mitaka:</div><div> <a href="https://review.openstack.org/#/c/213490/" target="_blank">https://review.openstack.org/#/c/213490/</a></div><div><br></div><div> And as i mentioned above Kuryr spec process depends on Neutron (and the specs that are sent</div><div> to Neutron core)</div></div></div></div></blockquote><div><br></div><div>I'll review it and provide feedback. 'Depending on Neutron' means requiring actual enhancement to the core platform that makes sense to be tracked/discussed in Neutron. Everything else can be tracked independently: this is the separation of concerns that we should strive for.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div class="h5"><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>Any opinions on that?<br><br></div>Gal.<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Tue, Oct 20, 2015 at 11:10 PM, Armando M. <span dir="ltr"><<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div><div dir="ltr">Hi folks,<div><br></div><div>During revision of the Neutron teams [1], we made clear that the neutron-specs repo is to be targeted by specs for all the Neutron projects (core + *-aas).</div><div><br></div><div>For this reason I made sure that the neutron-specs-core team +2 right was extended to all the core teams.</div><div><br></div><div>Be mindful, use your +2 rights with care: if you are core on a *-aas project, you should exercise that vote only for specs that pertain the project you're core of.</div><div><br></div><div>If I could use this email as a reminder also of the core hierarchy and lieutenant system we switched to in Liberty ([3]): if you have been made core by a lieutenant of a sub-system, please use your +2/+A only within your area of comfort and reach out for help if in doubt. </div><div><br></div><div>Reviews are always welcome though!</div><div><br></div><div>Cheers,</div><div>Armando</div><div><br></div><div>[1] <a href="https://review.openstack.org/#/c/237180/" target="_blank">https://review.openstack.org/#/c/237180/</a></div><div>[2] <a href="https://review.openstack.org/#/admin/groups/314,members" target="_blank">https://review.openstack.org/#/admin/groups/314,members</a></div><div>[3] <a href="http://docs.openstack.org/developer/neutron/policies/neutron-teams.html#core-review-hierarchy" target="_blank">http://docs.openstack.org/developer/neutron/policies/neutron-teams.html#core-review-hierarchy</a></div></div>
<br></div></div>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><span><font color="#888888"><br><br clear="all"><br>-- <br><div>Best Regards ,<br><br>The G. </div>
</font></span></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div></div></div><br></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div></div></div><div><div class="h5"><br><br clear="all"><div><br></div>-- <br><div>Best Regards ,<br><br>The G. </div>
</div></div></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>