<br><br><div class="gmail_quote">On Wed, Nov 7, 2012 at 12:13 PM, Russell Bryant <span dir="ltr"><<a href="mailto:rbryant@redhat.com" target="_blank">rbryant@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 11/07/2012 12:04 PM, Doug Hellmann wrote:<br>
><br>
><br>
> On Wed, Nov 7, 2012 at 11:40 AM, Thierry Carrez <<a href="mailto:thierry@openstack.org">thierry@openstack.org</a><br>
</div><div><div class="h5">> <mailto:<a href="mailto:thierry@openstack.org">thierry@openstack.org</a>>> wrote:<br>
><br>
> Hi everyone,<br>
><br>
> Incubation is currently an OpenStack project status that grants a<br>
> promising project more access to OpenStack shared resources, especially<br>
> in the CI, release management and QA space. That status lets the<br>
> promising project prove that it is ready to join other official<br>
> OpenStack core projects for the next full development cycle.<br>
><br>
> In the past governance the Project Policy Board was the only decider on<br>
> Incubation and Core inclusion. With the new governance, the Technical<br>
> Committee is still the only decider on Incubation status and still<br>
> proposes projects for Core inclusion, but the Board of Directors has the<br>
> possibility to veto that Core inclusion.<br>
><br>
> This creates an awkward process where a project could go all the way<br>
> through Incubation and be denied Core inclusion at the end of that<br>
> process, basically wasting OpenStack resources. We need to evolve the<br>
> Incubation process so that the question of whether a project belongs in<br>
> "Core" is fully resolved as early as possible. And define how a project<br>
> can enter, grow or exit the incubation process.<br>
><br>
> This also raises the question of whether "Core" should really be the<br>
> only destination of an Incubated project. Which triggers the very<br>
> question of what OpenStack Core actually is. For some it's the<br>
> collection of OpenStack projects that work well and complement each<br>
> other, for others Core should only include the IaaS pieces, for others<br>
> they should represent the bare minimum you need to implement to be able<br>
> to be called an "OpenStack Cloud"...<br>
><br>
><br>
> It would be healthy to allow the scope of projects managed by the<br>
> foundation to evolve over time to be broader than IaaS components. If we<br>
> need to define "OpenStack Cloud" for brand management, we should be<br>
> thinking about it at the different levels of the stack. There could be a<br>
> separate set of "core" projects for IaaS and PaaS, for example.<br>
<br>
</div></div>I agree that I'd like to see the project overall be inclusive instead of<br>
exclusive.<br>
<div class="im"><br>
> Once "Core" is defined we can evaluate the need for a category that<br>
> would still be in "OpenStack" but not have the "Core" label on it.<br>
> Incubation could then lead two ways.<br>
><br>
><br>
> It seems like we want a "supported" category for projects the TC feels<br>
> are worth spending foundation resources on but the BoD does not want to<br>
> include in "core" and require that deployers use them to be able to<br>
> claim they are an "OpenStack Cloud" as you mention above. So projects<br>
> would start out in the community, move to "incubated" and then to<br>
> "supported" after the incubation period is up. They could apply<br>
> separately for "core" status, after being declared "supported" by the TC.<br>
<br>
</div>This seems to be the crux of the issue. If the OpenStack mark is going<br>
to be wrapped up in what "core" is, then I think it seems fine to keep<br>
it very limited, and perhaps to minimal IaaS components, but *only* if<br>
we have a place for everything else that is a positive addition to go.<br>
A new category like "supported" seems like a great idea to me.<br>
<br>
My gut feeling of where the line would be is that Heat, Ceilometer, and<br>
Horizon would all be in this new category, while everything else would<br>
remain the core.<br></blockquote><div><br></div><div>That makes sense to me.</div><div><br></div><div>Doug</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Russell Bryant<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br>