<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 10, 2015 at 10:29 AM, 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">The TC is in the middle of implementing a fairly significant change in<br>
project governance. You can find an overview from Thierry on the<br>
OpenStack blog [1].<br>
<br>
Part of the change is to recognize more projects as being part of the<br>
OpenStack community. Another critical part was replacing the integrated<br>
release with a set of tags. A project would be given a tag if it meets<br>
some defined set of criteria.<br>
<br>
I feel that we're at a very vulnerable part of this transition. We've<br>
abolished the incubation process and integrated release. We've<br>
established a fairly low bar for new projects [2]. However, we have not<br>
yet approved *any* tags other than the one that reflects which projects<br>
are included in the final integrated release (Kilo) [3]. Despite the<br>
previously discussed challenges with the integrated release,<br>
it did at least mean that a project has met a very useful set of<br>
criteria [4].<br>
<br>
We now have several new project proposals. However, I propose not<br>
approving any new projects until we have a tagging system that is at<br>
least far enough along to represent the set of criteria that we used to<br>
apply to all OpenStack projects (with exception for ones we want to<br>
consciously drop). Otherwise, I think it's a significant setback to our<br>
project governance as we have yet to provide any useful way to navigate<br>
the growing set of projects.<br>
<br>
The resulting set of tags doesn't have to be focused on replicating our<br>
previous set of criteria. The focus must be on what information is<br>
needed by various groups of consumers and tags are a mechanism to<br>
implement that. In any case, we're far from that point because today we<br>
have nothing.<br>
<br>
I can't think of any good reason to rush into approving projects in the<br>
short term. If we're not able to work out this rich tagging system in a<br>
reasonable amount of time, then maybe the whole approach is broken and<br>
we need to rethink the whole approach.<br>
<br>
Thanks,<br>
<br>
[1] <a href="http://www.openstack.org/blog/2015/02/tc-update-project-reform-progress/" target="_blank">http://www.openstack.org/blog/2015/02/tc-update-project-reform-progress/</a><br>
[2] <a href="http://governance.openstack.org/reference/new-projects-requirements.html" target="_blank">http://governance.openstack.org/reference/new-projects-requirements.html</a><br>
[3] <a href="http://governance.openstack.org/reference/tags/index.html" target="_blank">http://governance.openstack.org/reference/tags/index.html</a><br>
[4]<br>
<a href="http://governance.openstack.org/reference/incubation-integration-requirements.html" target="_blank">http://governance.openstack.org/reference/incubation-integration-requirements.html</a><br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Russell Bryant<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</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>
</font></span></blockquote></div><br></div><div class="gmail_extra"><div class="gmail_default" style="font-family:monospace,monospace">I think these are great points Russell and agree completely. I'd also say that not only is their risk in rushing approval in the short time, I'd also say that in my opinion there's little or no advantage either. I like the idea of suspending things temporarily until we get the tagging and other details worked out a bit more.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">Thanks,</div><div class="gmail_default" style="font-family:monospace,monospace">John</div><br></div></div>