Get Involved and Contribute

Cloud Foundry is an open source project. Join our open ecosystem of cloud frameworks and services, add features, comment on design docs, report or fix a bug, contribute documentation or technical articles. We welcome your contribution.

The Cloud Foundry open source project is comprised of a number of different repositories. All of them can be found at, but here's a brief overview of the main projects to help you get started:


To learn more about Cloud Foundry, visit one or more of the following resources:

Meetups and Events

Come meet other CF newbies and pros at a Cloud Foundry meetup or event.

Globally * Pivotal Open Source Hub

United States * Silicon Valley, CA * San Diego, CA * Palo Alto, CA * Los Angeles, CA * Denver/Boulder, CO * Washington, DC * Boston, MA * St Louis, MO * Raleigh, NC * New York City, NY * Portland, OR * Austin, TX

Canada * Toronto, Canada

China * Beijing, China

Japan * Japan

Netherlands * Netherlands

Switzerland, Germany, Austria * Switzerland, Germany, Austria

United Kingdom / England * London, United Kingdom

Australia * Sydney, Australia

In 2013, we had our first Cloud Foundry User Conference. Visit the conference site to view session recordings and slides.

Ask Questions

Questions about the Cloud Foundry Open Source Project can be directed to our mailing lists.

File a Bug

Bugs can be filed using Github Issues within the various repositories listed above. Check the project's README for any specific instructions.

Please review our Public Trackers first to see what's already in the queue to be fixed.

Contribute to the Wiki

See something on the wiki that's missing or could use some clarification? Go ahead and update it. All you need are your GitHub credentials.

Contribute Code

Below are the general steps to make a code contribution. For each project, please review the repository's README to see if there are any other specific instructions.

  1. Ensure that you have either completed our CLA Agreement for individuals or are a public member of an organization that has signed the corporate CLA.

  2. Set your name and email (these should match the information on your submitted CLA):

     git config --global "Firstname Lastname"
     git config --global ""
  3. Fork the project's repository

  4. Create a feature branch (e.g. git checkout -b better_bosh) and make changes on your branch

  5. Push to your fork (e.g. git push origin better_bosh) and submit a pull request

If you have a CLA on file, your contribution will be analyzed for engineering quality and product fit prior to merging.

Note: All contributions need to be sent using GitHub Pull Requests, and we favor pull requests with very small, single commits with a single purpose. Your pull request is much more likely to be accepted if it includes tests and is small and focused with a clear message that conveys the intent of your change.