On 08/01/2016 09:39 AM, Thierry Carrez wrote: > But if a project is persistently single-vendor after some time and > nobody seems interested to join it, the technical value of that project > being "in" OpenStack rather than a separate project in the OpenStack > ecosystem of projects is limited. It's limited for OpenStack (why > provide resources to support a project that is obviously only beneficial > to one organization ?), and it's limited to the organization itself (why > go through the OpenStack-specific open processes when you could shortcut > it with internal tools and meetings ? why accept the oversight of the > Technical Committee ?).
A project can still be useful for everyone with a single vendor contributing to it, even after a long period of existence. IMO that's not the issue we're trying to solve. Cheers, Thomas Goirand (zigo) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
