<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 22 September 2016 at 00:46, reedip banerjee <span dir="ltr"><<a href="mailto:reedip14@gmail.com" target="_blank">reedip14@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Dear Neutron Core members,<div><br></div><div>I have a query regarding the procedure for inclusion in the Neutron Stadium.</div><div>I wanted to know if a project can apply for Big Tent and Neutron Stadium together ( means can a project be accepted in the Neutron Stadium and as a result into the Big Tent )</div><div><br></div><div>I was checking out the checklist in [1], and IMO , I think that we need to conform to the checklist to be added to the Neutron Stadium ( along with the other requirements like keeping in sync with the core neutron concepts)</div><div><br></div><div>But IIUC, certain items in the checklist would be completed if a project is already included in the Big Tent.</div></div></blockquote><div><br></div><div>I would not worry about those, as these are rather trivial to implement in conjunction with Stadium inclusion. I'd worry about the fork that the project relies on, which is a big show stopper for Stadium inclusion.</div><div><br></div><div>[1] <a href="https://github.com/openstack/tap-as-a-service/blob/master/setup.cfg#L50">https://github.com/openstack/tap-as-a-service/blob/master/setup.cfg#L50</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>So my doubt is ,should a project apply for the Big Tent first, and after inclusion, apply for Neutron Stadium ? Or can a project be integrated to Neutron Stadium and Big Tent simultaneously ( I am a bit sceptical about this though)?</div></div></blockquote><div><br></div><div>You are confusing the two things. A project either belongs to list [1] or list [2], and you can't be in both at the same time. To be part of either list a project must comply with a set of criteria. As for the latter, a couple of steps may sound like a catch 22: for instance you can't make docs available on docs.o.o unless you are in [2] and you can't be in [2] unless...and here's the trick, unless you are a point where you can successfully demonstrate that the project has substantial documentation (of any sort, API included). The process of 'demonstrating'/application for inclusion in list [2] follows the RFE submission process that we have adopted for a while, and that means submitting a spec. Since the request does not require a conventional design process, I was going to prepare an ad-hoc template and make it available soon. So watch the neutron-specs repo for updates.</div><div><br></div><div>In the meantime, I'd urge you to go over the checklist and make sure you can address the hard parts. </div><div><br></div><div>If you ask me, if you go with [1], it makes no sense to go and apply to be in [2].</div><div><br></div><div>HTH</div><div>Armando</div><div><br></div><div>[1] <a href="http://governance.openstack.org/reference/projects/">http://governance.openstack.org/reference/projects/</a></div><div>[2] <a href="http://governance.openstack.org/reference/projects/neutron.html">http://governance.openstack.org/reference/projects/neutron.html</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div><br></div><div>[1] <a href="http://docs.openstack.org/developer/neutron/stadium/governance.html#checklist" target="_blank">http://docs.openstack.org/<wbr>developer/neutron/stadium/<wbr>governance.html#checklist</a><span class="gmail-HOEnZb"><font color="#888888"><br></font></span></div><span class="gmail-HOEnZb"><font color="#888888"><div>-- <br><div><div dir="ltr"><div><div dir="ltr"><div>Thanks and Regards,<br>Reedip Banerjee</div><div>IRC: reedip</div><div><br></div><div><br><br><br></div></div></div></div></div>
</div></font></span></div>
<br>______________________________<wbr>______________________________<wbr>______________<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.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br></div></div>