Le 18/12/2013 16:37, Steven Dake a écrit :
In the early days of incubation requests, I got the distinct
impression managers at companies believed that actually getting a
project incubated in OpenStack was not possible, even though it was
sparsely documented as an option. Maybe things are different now that
a few projects have actually run the gauntlet of incubation and proven
that it can be done ;) (see ceilometer, heat as early examples).
But I can tell you one thing for certain, an actual incubation
commitment from the OpenStack Technical Committee has a huge impact -
it says "Yes we think this project has great potential for improving
OpenStack's scope in a helpful useful way and we plan to support the
program to make it happen". Without that commitment, managers at
companies have a harder time justifying R&D expenses.
That is why I am not a big fan of approach #3 - companies are unlikely
to commit without a commitment from the TC first ;-) (see chicken/egg
in your original argument ;)
We shouldn't be afraid of a project failing to graduate to
Integrated. Even though it hasn't happened yet, it will undoubtedly
happen at some point in the future. We have a way for projects to
leave incubation if they fail to become a strong emergent system, as
described in option #2.
Regards
-steve
Thanks Steven for the story. Based on your comments, I would change my
vote to #2 as it sounds like the most practical approach.
-Sylvain
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
