CCIF pulls out of the Open Cloud Manifesto

The Cloud Computing Interoperability Forum will acknowledge the criticisms of the closed process used to create the document, to be presented Monday.

In a post to the Cloud Computing Interoperability Forum (copied in full below), the original organizers of that group--Reuven Cohen, Sam Charrington, Jesse Silver, and David Nielsen--have announced that the CCIF will no longer be a signatory of the controversial Open Cloud Manifesto to be presented Monday:

When the Open Cloud Manifesto is officially released on Monday, March 30, the CCIF's name will not appear as a signatory. This decision comes with great pain, as we fully endorse the document's contents and its principals of a truly open cloud.

However, this community has issued a mandate of openness and fair process, loudly and clearly, and so the CCIF cannot in good faith endorse this document.

Knowing what we know now, we certainly would have lobbied harder to open the document to the forum before this uproar ensued.

This surprising move means not only that the list of signatories is shrinking further--I have confirmation that Google has refused to sign, along with the already well-known Amazon.com and Microsoft declinations --but that the only open alliance of any kind and one of the chief proponents of the document has backed out.

As I noted Saturday , I think the failure of the manifesto to launch as a secretly crafted, but complete, fully endorsed statement of principles is a sign of the expectation of open process we all expect these days.

Cohen et al note above that they still "fully endorse the document's content and its principals of a truly open cloud." However, they also acknowledge that they failed to grasp the sense of community ownership of the CCIF and that their independent actions were not consistent with the goals of the community.

The post goes on to discuss the need for better tools and processes to identify and support the CCIF's core principles, and proposes a formalization of the organization to enable that.

Here is the post in its entirety:

Dear Friends,

It is with an eye toward an open future that we address the many apt criticisms levied at the Cloud Computing Interoperability Forum (CCIF) and the difficult circumstance in which this community finds itself.

As the organizers of the community, we would like to make our intentions clear. The following letter is not an edict or decree. It is a heartfelt attempt to reach out to our fellow community members so we might begin to move past recent events and together discuss our options.

*An Apology*

While sifting through this week's enthusiastic and well-argued posts, one issue rose to painful clarity: There is not, and has never been, an agreed-upon definition of the CCIF. As organizers, we have "announced," at various times, conflicting statements on how "our members" should view this forum.

These definitions range from "cloud advocacy group," which implies membership and organized offline activity, to the much narrower "e-mail discussion group." Due to our failure to better define our project, each community member has been left to his or her own devices, latching onto any number of definitions.

At some point over the last few months, the community began to feel a sense of ownership of and membership in the entity CCIF. Until this week, we had not fully appreciated that the CCIF had become the de facto membership organization for interoperability stakeholders.

Under this new premise, it is clear that our direct and private engagement, in the name of the CCIF, vis a vis the Open Cloud Manifesto , may be viewed as a breech of this community's norms. For this oversight, we take full responsibility.

*Open Cloud Manifesto*

To this end, when the Open Cloud Manifesto is officially released on Monday, March 30, the CCIF's name will not appear as a signatory. This decision comes with great pain, as we fully endorse the document's contents and its principals of a truly open cloud. However, this community has issued a mandate of openness and fair process, loudly and clearly, and so the CCIF can not in good faith endorse this document.

Knowing what we know now, we certainly would have lobbied harder to open the document to the forum before this uproar ensued.

*Governance and the Future of the CCIF*

Therein lies the problem. Consider this: even if we had secured the OK to open the manifesto for discussion before signing in the name of CCIF, there would have been no mechanism by which to formally make changes or give approval. This is, or at least in our opinion ought to be, unacceptable to most of the community.

Therefore, though this is simply a proposal to get us started considering next steps, we feel that it is time for some degree of formalization. This means governance and, of course, some or all of the following components:

  1. Formal mission statement, laws and articles
  2. Formal membership structure
  3. A board or other defined leadership structure
  4. Formal decision-making mechanism
  5. Committees and/or formal interest groups
  6. Goals, deliverables, and activities
  7. Wikis, Web sites, and other properties governed by our laws and articles
  8. Financial backing and/or formal associations with industry

If the community coalesces around formalization, CCIF's organizers will go to the greatest possible lengths to ensure the process unfolds openly and in the best interests of the cloud-computing community at large, not for the benefit or self-aggrandizement of any specific member or interest group.

Regarding the specifics of the outcome, we are not prepared to propose or oppose any plan. If and when the time is right, we will create a wiki or other mechanism to hash out details. For now, let's start discussing whether this is the right direction for the CCIF.

Thank you and best wishes to all,

Sam Charrington, Reuven Cohen, Dave Niesen, Jesse Silver (alphabetical)

About the author

    James Urquhart is a field technologist with almost 20 years of experience in distributed-systems development and deployment, focusing on service-oriented architectures, cloud computing, and virtualization. James is a market strategist for cloud computing at Cisco Systems and an adviser to EnStratus, though the opinions expressed here are strictly his own. He is a member of the CNET Blog Network and is not an employee of CNET.

     

    Join the discussion

    Conversation powered by Livefyre

    Don't Miss
    Hot Products
    Trending on CNET

    HOT ON CNET

    Looking for an affordable tablet?

    CNET rounds up high-quality tablets that won't break your wallet.