An Interview With Cloud Foundry Foundation CEO Sam Ramji [Video]

DZone 's Guide to

An Interview With Cloud Foundry Foundation CEO Sam Ramji [Video]

From SpringOne conference, an interview with the head of the CF Foundation who describes the futures of CF and what's going on now.

· Cloud Zone ·
Free Resource

A couple of months ago at the Cloud Foundry Summit, I tried to grab Sam Ramji, CEO of the Cloud Foundry Foundation, to do a short interview.  Unfortunately, the stars didn’t align and it didn’t happen. At SpringOne Platform, however, I had better luck.

Sam, who led off the keynotes on day two, sat and talked to me about Cloud Foundry’s origins, what’s going on today and what its goals are for the future.

Take a listen

Some of the Ground Sam Covers:

  • Cloud Foundry began at VMware in 2009 and was open sourced back in 2011. The foundation itself was set up a year and half ago.
  • CloudFoundry.org was established to increase the velocity of contributions (over the last year, more than 2,000 individuals outside of  the core companies have contributed.)
  • While they want to grow the foundation, they need to be thoughtful on how they grow.
  • What drew Sam to the CEO opportunity and the role that APIs and Warner music played in his decision.
  • The foundation’s goals:
    1. Increase diversity of contributions.
    2. Increase the foundation’s population, predominantly via end users.
    3. Determine how best to build a framework that will allow to the effort to survive and thrive over the next 20 years.

Extra Credit Reading

  • Talking Cloud Foundry Foundation: OpenStack summit Austin, Youtube.
  • SpringOne: The Spring Platform, Where it's Been and Where its Going, Barton’s Blog.
  • SpringOne: Native Hybrid Cloud: The Pivotal Cloud Foundry Developer Platform in a Box, Barton’s Blog.
  • SpringOne: When Web Companies grow up they turn into Java Shops, Barton’s Blog.

Related Refcard:

cloudfoundry ,paas ,cloud ,go language

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}