October 24, 2014 | Written by: Christopher Ferris
Share this post:
Today marks an important milestone along the path to open governance for the Cloud Foundry open source platform as a service (PaaS) initiative. The founding sponsors have been hard at work since this past spring, hammering out the governance model and drafting legal documents for the incorporation of the Cloud Foundry Foundation. Those documents are now available for public review.
An open governance model is vitally important for the long-term success of any open source initiative. In that same spirit, the founding Cloud Foundry sponsors strongly encourage all stakeholders to review and comment on these documents.
I’m really excited by how well things have progressed, and how far we have come with the Cloud Foundry initiative since IBM’s announcement last summer that it would the open source initiative and collaborate with Pivotal on a path to open governance. I’ve included a list of some of the key milestones over the past year and a half at the end of this blog post. As you can see, there has been a lot of activity.
IBM’s involvement goes well beyond the development of open governance. Over the course of the past year and a half, IBM (very) actively engaged in the development of Cloud Foundry open source components. As you might expect, given that IBM Bluemix depends heavily on Cloud Foundry, IBM has sent a total of eleven IBMers through the Cloud Foundry Open Dojo program. Nine of those developers work on my team and are dedicated to the success of Cloud Foundry. You could say that it’s their “day job”.
Those developers that have completed their Dojo stint are now considered “dedicated committers” in the lexicon of the new open governance model proposed by the founding sponsors. They are working side by side, either locally or remotely, with others on the various Cloud Foundry projects, working on stories assigned by the project’s product manager.
IBM now has developers engaged in six of the Cloud Foundry OSS project teams, and we hope to grow this over time. Thus far, the collaboration has been fantastic. The IBMers gained deep insight into the various projects on which they were working through the paired development model practiced by the Pivotal engineering teams, and the Pivots gained useful insights from the IBMers, many of whom had many years of deep experience and expertise with the challenges of large scale distributed computing.
Since July 2013, we’ve been actively engaged in helping to test out and tune the governance model, and to adapt it where necessary. Because of this, I am confident that the model we have outlined in the draft governance will be an effective starting point for the new Foundation. We’ve also built-in sufficient autonomy of the governance over the technical side of things such that the governance model can be adapted by the technical community as needed to ensure that the project continues to thrive, and to ensure the greatest levels of transparency and inclusiveness of all who wish to contribute.
Over the course of the next month or so, the founding sponsors will continue working on hammering out some more of the specifics of the governance model. This includes work on what we have been calling the operational governance documents of the technical side of the foundation as well as more work to flesh out the model for management and oversight of the Cloud Foundry branding.
In short, things are really starting to heat up in preparation for launching the new Cloud Foundry Foundation, and it is really starting to get exciting! We’ll be reviewing the draft governance on this month’s Community Advisory Board meeting, Wednesday, Oct. 29 at 11 am ET. So, should you have any questions or concerns, please do join us and engage in the discussion.
Key milestones along Cloud Foundry’s path to open governance:
– August 2013 – “Community Pair” concept launched by Pivotal; to improve responsiveness to community issues and pull requests
– September 2013 – PlatformCF Summit in San Francisco with four-hundred and fifty attendees
– September 2013 – IBM contributes IBM WebSphere Liberty Buildpack to Cloud Foundry
– October 2013 – established a ten member Community Advisory Board with monthly open forum calls to discuss progress with the open source development and to review incubation matriculation and graduation proposals
– October 2013 – established cloudfoundry-incubator Github org and process
– October 2013 – IBM contributes Admin UI to cloudfoundry-incubator Github org
– December 2013 – opened up public Pivotal Trackers for many of the open source projects
– December 2013 – Pivotal publishes Cloud Foundry Contribution Guidelines and Coding Standards
– January 2014 – Pivotal publishes Development Process for the Cloud Foundry OSS project
– February 2014 – Pivotal announces plans to establish Cloud Foundry Foundation for open governance of Cloud Foundry open source initiative; IBM and five others sign on as Platinum Sponsors
– March 2014 – Eclipse Tools for CF 1.6 released and project moved from Eclipse to Cloud Foundry; first release reflecting collaboration between IBM and Pivotal
– April 2014 – IBM, Fidelity and Pivotal collaborate on enabling integration between Cloud Foundry UAA and OpenStack Keystone
– May 2014 – Eight Gold level sponsors of the new Cloud Foundry Foundation announced
– June 2014 – Performance Acceptance Tools contributed to Cloud Foundry incubator by IBM
– June 2014 – CF Summit in San Francisco with nine-hundred attendees; more than double the attendance of the previous Summit
– June 2014 – New Gold and Silver level sponsors announced, bringing total intended sponsors of the new Cloud Foundry Foundation to thirty-four
– August 2014 – IBM, SAP, Cloud Credo and Pivotal collaborate on integrating Docker into Cloud Foundry Diego
– October 2014 – Draft governance documents for new Cloud Foundry Foundation published for public review