There is a summit session in Vancouver with some ideas in https://etherpad.openstack.org/p/YVR-ops-tags. I have added the links there as reference material. Building on a previous work from other communities would be an interesting possibility. We don¹t need to wait till then so comments on the ether pad or mailing list are welcome. Tim On 5/5/15, 8:31 PM, "Stefano Maffulli" <stefano at openstack.org> wrote: >Hello folks, > >in PHL meeting the discussion on project tags[1] highlighted that >operators are looking for answers to questions like: > > * Are fixes backported? Or Consumes Master to get fixes? > * Is it packaged? > * Is it stable? Mature? > * is it tested in Tempest/Rally/whatever so I can test before I >deploy changes? > * What API Version does it offer > * Is documentation available > >I think these questions come down to identifying a 'maturity model' or >'evaluation model' that can help people select OpenStack software to >solve their needs. The good news is that other communities have been in >similar situation and looking at them can provide a path for us to >follow (and mistakes to avoid). > >Apache and Polarsys (an Eclipse working group) have each developed a >maturity model for their own purposes[2][3]. Each one is focused on >relevant aspects to the respective community, but all are similar in how >they are produced. One part of the model comes directly from metrics >retrieved from repositories (such as this diversity metric, which we >track with the diverse-affiliation tag[4]), a part needs human >intervention (such as the release:managed or release:has-stable-branches >which we add semi-manually [4]). > >I'd like to continue the conversation about an OpenStack Maturity Model >that can be consumed by users downstream. Any suggestions on how to move >this project forward? > >/stef > > >[1] https://etherpad.openstack.org/p/PHL-ops-tags >[2] >https://community.apache.org/apache-way/apache-project-maturity-model.html >[3] http://dashboard.castalia.camp/documentation/ and >https://polarsys.org/wiki/Maturity_Assessment_WG >[4] https://review.openstack.org/#/c/179258/ and >http://governance.openstack.org/reference/tags/team_diverse-affiliatio > >_______________________________________________ >OpenStack-operators mailing list >OpenStack-operators at lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators