On 02/16/2012 07:18 PM, John Mark Walker wrote:
Nick,
Your comments are extremely helpful. Can you take a crack at integrating
your comments into the document Shanley sent around? Dont' worry if the
language is ugly - we can always make it more polished later.
Sure, my proposed modifications enclosed.
Can we call an emergency meeting in the very near future to go over what
we have, make adjustments "in real time", and resolve not to end the
meeting until we have this hashed out?
Agreed. Should we start a Doodle to find an appropriate time?
Nick
I feel a sense of urgency here, and I don't want to lose the opportunity
to capitalize on the all of the open cloud discussions taking place
right now.
-JM
On Thu, Feb 16, 2012 at 6:02 AM, Nicolas Barcet <[email protected]
<mailto:[email protected]>> wrote:
This looks great to me, thanks a lot for putting it together. I have
a few remarks that would improve the document a bit from my point view:
a) should decision be motivated? If so, it would allow for the
vendor to fix easier but would require for the ones voting against
to summarize why they are doing so (votes and remarks should remain
anonymous to the people outside the board).
b) the form submission should stipulate that for services which are
not openly available (source, binaries, or open remote access) the
board and/or community members designated by the board should be
given temporary access to the software (license/binary/online
account) upon request during the evaluation phase and at any point
after certification to verify continued compliance,
c) vendors should designate an official point of contact for any
questions arising during the certification and for the duration of
certification.
d) vendors should pledge
-> to inform the board of any changes that may cause the
certification to be reviewed (in the software or in their legal terms),
-> as well as provide best efforts to maintain their openess on the
submited product(s) over time.
e) Inform them where community discussions will take place and that
the discussion are public. Make them agree that they have a right
of response but that they agree on the process and the fact that
motivated and non offensive comments will not be removed.
I am sure all this can be put in a better wording, but would
certainly help toward the openness of the process.
Nick
On 02/15/2012 10:25 PM, Shanley Kane 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
<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 Procedure for Products and
Services *
The OCI review process enables the community of cloud computing
users
and providers 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 is invited to
participate in community discussion via the OCI Certification
mailing list.
* The OCI review process is specifically focused on applying the
community-derived Open Cloud Principles, constituting the
existing
community definition of open cloud, to products and services.
Evolutions to 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 cloud community to contribute to the
application of the Open Cloud Principles.
* 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.
* Complete and submit the template (below) to the Certification
mailing list. Submissions will be posted publicly on the OCI
list
archive.
* 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.
* The Certification Committee will review community discussion and
create a summary and recommendation, submitted to the OCI
Board and
the Certification mailing list.
* 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 certification. A
quorum of the board must be reached in favor of certifying the
product or service in order for the vote to pass.
* 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.
*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. /
Open Cloud Initiative Certification Procedure for Products and Services
The OCI review process enables the community of cloud computing users and
providers 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 is invited to participate in
community discussion via the OCI Certification mailing list.
The OCI review process is specifically focused on applying the
community-derived Open Cloud Principles, constituting the existing community
definition of open cloud, to products and services. Evolutions to 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 cloud community to contribute to the
application of the Open Cloud Principles.
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.
Complete and submit the template (below) to the Certification mailing list.
Submissions will be posted publicly on the OCI list archive.
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.
The Certification Committee will review community discussion and create a
summary and recommendation, submitted to the OCI Board and the Certification
mailing list.
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 certification. A quorum of the board must be reached in
favor of certifying the product or service in order for the vote to pass.
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, the board will motivate the reasons. The 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.
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?
Where can your product be tested [1]?
Who should we contact to obtain further information (name and email address)?
Please attach any supporting technical documentation not available on the open
internet.
By submitting its product for certification, the vendor pledges to:
* inform the board of any changes that may cause the certification to be
reviewed (in the software or in their legal terms),
* provide best efforts to maintain the product openness on the submitted
product(s) over time.
The vendor also acknowledges and agrees that community discussions will take
place at [XXXXX] and that the discussion are public. The vendor has a right of
response but agrees on the process and the fact that motivated and non
offensive comments in this dicussion will not be removed.
Do you accept the above term?
Name, title and email address of submitter:
[1] Note that if the product is not openly available (source, binaries, or
open remote access) the board and/or community members designated by the board
should be given temporary access to the software (license/binary/online
account) upon request during the evaluation phase and at any point after
certification to verify continued compliance.
