[openstack-dev] Avoiding regression in project governance

Flavio Percoco flavio at redhat.com
Thu Mar 12 00:17:38 UTC 2015

On 11/03/15 19:06 +0000, Tim Bell wrote:
>> -----Original Message-----
>> From: Stefano Maffulli [mailto:stefano at openstack.org]
>> Sent: 11 March 2015 03:16
>> To: openstack-dev at lists.openstack.org
>> Subject: Re: [openstack-dev] Avoiding regression in project governance
>> On Tue, 2015-03-10 at 15:23 -0700, James E. Blair wrote:
>> > The holy grail of this system would be the "suitable for production
>> > deployment" tag, but no one has figured out how to define it yet.
>> Are crazy ideas welcome in this phase?
>> I start with 2 below:
>> Preface: an idea circulates about visually displaying in a web page the
>> projects.yaml file and the tags in there. Visitors would be able to browse the list
>> of projects and sort, pick, search and find what they need from a nice
>> representation of the 'big tent'.
>> 1) how about we pull the popularity of OpenStack projects as reported in the
>> User Survey and display such number on the page where we list the projects?
>> What if, together with the objective tags managed by TC and community at
>> large, we show also the number of known deployment as guidance?
>I think we can make this work. Assuming more than N (to my mind > 5  or so) deployments report they are using project X, we can say that this is used in production/POC/... and the number of nodes/hypervisors/etc.
>This makes it concrete and anonymous to avoid the fishing queries. It also allows our community to enter what they are doing in one place rather than answering multiple surveys. I am keen to avoid generic queries such as "How many hypervisors are installed for public clouds using Xen" but if we have an agreement that >5 avoids company identification, I feel this is feasible.
>It does help address the "maturity" question concretely. If it's in prod in 200 deployments, I would consider this to be reasonably mature. If there is only 1, I would worry.

I'm not convinced this is a fair metric. What if I tell you, there's
just 1 large deployment? or that there's just 1 deployment that has
been running the service for quite a bit?

It's true that the more deployments there are, the easier it is to
trust a project's maturity but I'd be worry about people considering
that the only metric and not giving new projects a chance.



Flavio Percoco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150311/c0fff9b0/attachment.pgp>

More information about the OpenStack-dev mailing list