Over a million developers have joined DZone.

The Cloud Foundry Foundation One Step Closer to Reality

DZone 's Guide to

The Cloud Foundry Foundation One Step Closer to Reality

· Cloud Zone ·
Free Resource

Today is another exciting day in the Cloud Foundry community, with the Cloud Foundry Foundation taking a giant step toward becoming official: its draft governing documents and bylaws have been posted for public review.

Cloud Foundry already seems to be generally accepted by enterprises as the de facto PaaS standard, and the formation of the Foundation only strengthens that.

ActiveState proudly supports the Foundation and is a founding gold member, so we are thrilled to see this major milestone achieved.

The important key messages in the governing documents include:

  • A "governance by contribution" model
  • Apache 2.0 licensing and and Apache style CLAs
  • A separation of the Foundation's business operations and technical governance
  • A strategy council to represent member companies
  • A community user advisory board to represent the user community
  • A strong focus on preserving IP cleanliness
  • An equal opportunity to participate
  • An open planning process

If you are interested in the future direction and governance of Cloud Foundry, please read the documents and submit your comments. (If you don't want to post your feedback publicly, please feel free to submit your comments to me and I'll pass them along.) There will be also a discussion on the public Cloud Foundry Community Advisory Board call on October 29. (If you are unable to make that call, we will post a summary of it here in our blog shortly thereafter, as usual.)

To learn more about how Stackato uses Cloud Foundry (and Docker), please see our CTO's post from June, Stackato and Lessons Learned with Cloud Foundry. We believe that, in the Cloud Foundry ecosystem, everybody wins, and we can't wait for the Foundation to finally launch!



Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}