<div dir="ltr"><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 18, 2013 at 6:18 AM, Daniel P. Berrange <span dir="ltr"><<a href="mailto:berrange@redhat.com" target="_blank">berrange@redhat.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 class=""><div class="h5">On Wed, Dec 18, 2013 at 11:40:21AM +0100, Thierry Carrez wrote:<br>
> Hi everyone,<br>
><br>
> The TC meeting yesterday uncovered an interesting question which, so<br>
> far, divided TC members.<br>
><br>
> We require that projects have a number of different developers involved<br>
> before they apply for incubation, mostly to raise the bus factor. But we<br>
> also currently require some level of diversity in that development team:<br>
> we tend to reject projects where all the development team comes from a<br>
> single company.<br>
><br>
> There are various reasons for that: we want to make sure the project<br>
> survives the loss of interest of its main corporate sponsor, we want to<br>
> make sure it takes into account more than just one company's use case,<br>
> and we want to make sure there is convergence, collaboration and open<br>
> development at play there, before we start spending common resources in<br>
> helping them integrate with the rest of OpenStack.<br>
><br>
> That said, it creates a chicken-and-egg issue: other companies are less<br>
> likely to assign resources and converge to a project unless it gets<br>
> blessed as THE future solution. And it's true that in the past a lot of<br>
> projects really ramped up their communities AFTER being incubated.<br>
><br>
> I guess there are 3 options:<br>
><br>
> 1. Require diversity for incubation, but find ways to bless or recommend<br>
> projects pre-incubation so that this diversity can actually be achieved<br>
><br>
> 2. Do not require diversity for incubation, but require it for<br>
> graduation, and remove projects from incubation if they fail to attract<br>
> a diverse community<br>
><br>
> 3. Do not require diversity at incubation time, but at least judge the<br>
> interest of other companies: are they signed up to join in the future ?<br>
> Be ready to drop the project from incubation if that was a fake support<br>
> and the project fails to attract a diverse community<br>
<br>
</div></div>2 and 3 don't look all that different to me. Are you saying that 3<br>
does not have any 'diversity' requirement for graduation ?<br>
<div class="im"><br>
> Personally I'm leaning towards (3) at the moment. Thoughts ?<br>
<br>
</div>Where is the current definition of the "purpose" of the Incubation<br>
process ?<br>
<br>
I found this page but it has a disclaimer saying it might be<br>
outdated, but the "new" page doesn't articulate any clear<br>
purpose<br>
<br>
<a href="https://wiki.openstack.org/wiki/Governance/Approved/Incubation" target="_blank">https://wiki.openstack.org/wiki/Governance/Approved/Incubation</a></blockquote><div><br></div><div><div class="gmail_default" style="font-size:small">
The most current approved list is at <a href="http://git.openstack.org/cgit/openstack/governance/tree/reference/incubation-integration-requirements">http://git.openstack.org/cgit/openstack/governance/tree/reference/incubation-integration-requirements</a> (we're working on publishing those to a more readable format and updating wiki references).</div>
<br></div><div><div class="gmail_default" style="font-size:small">Doug</div><br></div><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">
<br>
<br>
Assuming for a minute the points from that page are still<br>
at least somewhat valid<br>
<br>
[quote]<br>
- Sustainable development processes<br>
- Growing the core development team<br>
- Establishing an initial user base<br>
- Maturing the software to an acceptable level of stability<br>
- Integration with OpenStack processes around testing, releases, and community management<br>
[/quote]<br>
<br>
Then my interpretation is that 'Growing the core development team'<br>
implicitly covers 'ensuring diversity'. As such I'd say option 2<br>
is appropriate - no requirement for incubation, but mandate it for<br>
graduation.<br>
<br>
Regards,<br>
Daniel<br>
<span class=""><font color="#888888">--<br>
|: <a href="http://berrange.com" target="_blank">http://berrange.com</a> -o- <a href="http://www.flickr.com/photos/dberrange/" target="_blank">http://www.flickr.com/photos/dberrange/</a> :|<br>
|: <a href="http://libvirt.org" target="_blank">http://libvirt.org</a> -o- <a href="http://virt-manager.org" target="_blank">http://virt-manager.org</a> :|<br>
|: <a href="http://autobuild.org" target="_blank">http://autobuild.org</a> -o- <a href="http://search.cpan.org/~danberr/" target="_blank">http://search.cpan.org/~danberr/</a> :|<br>
|: <a href="http://entangle-photo.org" target="_blank">http://entangle-photo.org</a> -o- <a href="http://live.gnome.org/gtk-vnc" target="_blank">http://live.gnome.org/gtk-vnc</a> :|<br>
</font></span><div class=""><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></div></div>