On 09/05/2014 07:39 AM, Robert Collins wrote:
> On 5 September 2014 23:33, Sean Dague <s...@dague.net> wrote:
>
>> I think realistically a self certification process that would have
>> artifacts in a discoverable place. I was thinking something along the
>> lines of a baseball card interface with a short description of the
>> project, a list of the requirements to deploy (native and python), a
>> link the the API docs, a link to current test coverage, as well as some
>> statement on the frequency of testing, stats on open bugs and current
>> trending and review backlog, current user testimonials. Basically the
>> kind of first stage analysis that a deployer would do before pushing
>> this out to their users.
>
> Add into that their deployment support - e.g. do they have TripleO
> support // Chef // Fuel // Puppet etc etc etc.
ACK, good points. I expect packaging might go on that list as well.
I won't pretend I've got the whole baseball card self cert thing worked
out, just trying to sketch an idea that might bear fruit.
-Sean
--
Sean Dague
http://dague.net
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
