Making Open Work
May 8–9, 2017: Training & Tutorials
May 10–11, 2017: Conference
Austin, TX

By every need necessary: A Cloud Foundry roadmap update

Chip Childers (Cloud Foundry Foundation)
11:50am12:30pm Wednesday, May 10, 2017
Location: Meeting Room 13 (Sponsored)

What you'll learn

  • Explore current and future efforts from Cloud Foundry


Open source projects are unique in that they are constantly mutating, based on user need, core committers, and councils dedicated to overseeing their evolution. While some open source projects can grow haphazardly, like a house with no blueprint, Cloud Foundry was designed to ensure a balance between competing interests, ingrained processes (like “pairing”) that improve quality and developer satisfaction, and vital collaboration among organizations. The community and culture within Cloud Foundry are comprised of practical, well-documented processes, and strong developers move at an ultrahigh velocity and keep an open mind about all new projects.

Chip Childers walks you through current and future efforts of the Cloud Foundry project teams, including Runtime PMC, CAPI, Diego, Garden, BOSH, and the Open Service Broker API, mapping out the evolution of these projects, their councils, and the implications of these updates for Cloud Foundry users.

This session is sponsored by Cloud Foundry Foundation.

Photo of Chip Childers

Chip Childers

Cloud Foundry Foundation

A proven DevOps visionary and leader, Chip Childers is vice president of technology at the Cloud Foundry Foundation. Previously, Chip was vice president of product strategy at CumuLogic and spent more than 15 years in engineering leadership positions within the service provider industry, including work at SunGard Availability Services and Qwest Solutions. Chip has served on the board of directors for the Distributed Management Task Force and is a member of the Apache Software Foundation.