Open Stack

Rob - if additional tests are added down the road as we build out the tests, will it require a yay/nay vote from all the providers of the certified products. That may be democratic but would prefer giving them a few months heads up/alerts/test fail notifications but not have push back. The idea here is that the set of tests may not be complete. In spirit they are to ensure the functionality desired.
Regards
Malini

From: Auld, Will [mailto:will.auld at intel.com]
Sent: Friday, May 02, 2014 8:09 AM
To: Rob_Hirschfeld at Dell.com; mark at openstack.org
Cc: Defcore-committee at lists.openstack.org
Subject: Re: [OpenStack-DefCore] Please review - lexicon, Public APIs only & capabilities definition text

Rob,

I am find with that, it already said that the requirements are defined in the license and that is really good enough.

Thanks,

Will

From: Rob_Hirschfeld at Dell.com<mailto:Rob_Hirschfeld at Dell.com> [mailto:Rob_Hirschfeld at Dell.com]
Sent: Friday, May 02, 2014 6:41 AM
To: Auld, Will; mark at openstack.org<mailto:mark at openstack.org>
Cc: Defcore-committee at lists.openstack.org<mailto:Defcore-committee at lists.openstack.org>
Subject: RE: [OpenStack-DefCore] Please review - lexicon, Public APIs only & capabilities definition text

Will,

I think you are expanding the basic definition with other information.  You are correct about the license requirement but it is beyond the definition of core capability here.   I'm concerned that our lexicon will become unwieldy if we have to remind people of the full context of each term.

Rob


Core Capability:  A capability all commercial products are expected to include when marketed as "OpenStack", to ensure interoperability between such products, which will be implemented via requirements in trademark licenses granted by the foundation. The requirements will include both "Designated Sections" and "Capabilities"  defined by the technical committee.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20140502/936d6443/attachment-0001.html>