Shanley, Thanks for pushing this along. Simon and I spoke about it last night in the context of getting something out for cloud connect but I'm tempted to let the open cloud noise die down a bit and he didn't want to rush something out. I also spent a few hours running through it with Krishnan today following his post<http://www.cloudave.com/17127/open-cloud-initiative-is-dead-long-live-oci/> — he wanted us to basically go all open source (e.g. skew towards the open crowd) or drop it altogether (e.g. skew towards the closed crowd), neither of which is going to happen sfaict. At the end of the day I think he agreed with the definition but worries about whether we'll be able to get a critical mass (something I'm less worried about).
Assuming we agree, I'd like to see the consensus decision making<http://en.wikipedia.org/wiki/Consensus_decision-making>process more clearly defined as following the IETF process<http://en.wikipedia.org/wiki/Consensus_decision-making#IETF_rough_consensus_model>— e.g. RFC 2418 Section 3.3 <http://tools.ietf.org/html/rfc2418#section-3.3>. I also considered the Wikipedia consensus process<http://en.wikipedia.org/wiki/Wikipedia:Consensus>but think it's a bit too much. Comments inline: On Wed, Feb 15, 2012 at 4:25 PM, Shanley Kane <shanley.k...@gmail.com>wrote: > *The Certification Committee is tasked with determining the process by > which given products or services are found to be compliant with the Open > Cloud Principles via community consensus, and how the process can be > healthfully and effectively managed.* > > Following a brief workshop on Friday, Feb 3 2012 which Sam Johnston, John > Mark and myself attended, we decided to launch the certification procedure > at Cloud Connect Event (February 13-16) as several board members will be > attending and it will provide a great platform for community evangelism. > > The Certification Committee has come up with a procedure based on various > Board and committee discussions as well as with the guidance of similar > organizations such as the Open Source Initiative. (Please review their > certification process here: http://www.opensource.org/approval) > > Please review the draft and provide any edits by end of day. > > The Certification Committee plans to post the certification procedure and > mailing list TOMORROW, THURSDAY FEB 16 and begin promoting it, including > but not limited to press briefings, etc. We may try to post a press release > early next week as well. > > Cheers > Shanley > ________________________ > > > *Open Cloud Initiative Certification Process for Cloud Computing Products > and Services * > > The OCI certification process enables the cloud computing community to > apply the requirements for Open Cloud, as described in the Open Cloud > Principles document, to products and services via open and transparent > discussion. Through the review process, products and services can be > determined by the community to satisfy open cloud principles and thus > approved to use the Open Cloud Initiative certification mark. > > *Guidelines: * > > - Any member of the cloud computing community may submit a product or > service for review. > - Any member of the cloud computing community may participate in the > community > consensus process. > - Evolution of the Open Cloud Principles themselves are subject to a > separate community consensus process. > > *Purpose of the Process: * > > - Certify products and services as meeting existing community > standards for open cloud, as defined in the Open Cloud Principles document. > - Provide a framework for the application of the Open Cloud Principles > by the community. > - Promote adoption of the Open Cloud Principles via open and > transparent discourse and community processes. > - Enable Open Cloud certification review of products and services to > take place in a timely fashion (no more than 90 days). > > > *Submitting a Product or Service for OCI Certification: * > > - Familiarize yourself with the Open Cloud Principles and subscribe to > the Certification mailing list. [OK] > - Complete and submit the template (below) to the Certification > mailing list. Submissions will be posted publicly on the OCI list archive. > [OK] > - The community is invited to discuss the submitted product or service > on the Certification mailing list. Discussion will be open for at least 30 > days and will not exceed 60 days. [OK] > - The Certification Committee will review community discussion and > create a summary and recommendation, submitted to the OCI Board and the > Certification mailing list. [OK] > - The OCI Board will consider the product or service at the next > monthly meeting of the board. The board may request additional information > from the community before proceeding. If no additional information is > required, the board will vote on ratification of the > communitycertification. A quorum of the board must be reached in favor of > certifying > the product or service in order for the vote to pass. [BOARD JUST HERE TO > RATIFY - EG IN THE CASE THAT THERE IS INSUFFICIENT/BIASED/ETC DISCUSSION] > - The Certification Committee will report back to the Certification > List with the decision and a summary of any board discussion. If the > Certification did not pass, another party may re-submit the product or > service if changes or alterations to it, or the Open Cloud Principles > themselves, would merit redress. If Certification is approved, the product > or service in question will be approved to use the Open Cloud logo and will > be displayed as such on the Open Cloud Initiative website, until such > time as revoked by way of subsequent review. > > > *Template for Submission > * > *Name of Product or Service: * > > *Web address where information about the product or service can be found: > * > * > * > *Web address where technical documentation about the product or service > can be found: * > * > * > *Brief description of the product or service: * > * > * > *How does the product or service use Open Standard formats to represent > user data and mata data? * > * > * > *How does the product or service expose functionality via Open Standard > interfaces? * > * > * > *Is there any other information the community should be aware of > pertaining to how the product or service complies with the Open Cloud > Principles document? * > * > * > * > * > *Please attach any supporting technical documentation not available on > the open internet. * >
