The State of FinOps 2022 Survey is Now Open

How to contribute

FinOps has become a required practice at many large organizations, but it’s also a nascent discipline and constantly evolving with cloud. This means that its best practices and principles will change over time as practitioners learn new skills, make new discoveries, and find new ways to better operationalize cloud cost management.

The open source FinOps Framework documents these changes with contributions from FinOps practitioners. This could be adding a FinOps story to one of our projects, fixing a simple typo or helping add completely new content.

How to submit changes to the FinOps Framework

If you see something that needs to be updated, augmented, or removed, we want to hear about it. This project is by the community and for the community and your voice matters.

There are multiple ways to submit changes:

  • Make a commit using the GitHub GUI and submit it for review
  • Submit an update or new content via this Google form which automatically creates a GitHub issue
  • Create an issue directly via GitHub
  • Reach out to the members and team in the #framework slack channel

Review process

Changes to each respective section of this site will be reviewed during FinOps Foundation team meetings, or meetings with the Technical Advisory Council. During these council meetings, commits and Pull Requests will be reviewed and voted upon to be merged.

The FinOps Foundation team uses automation tools to rebuild the site multiple times a week to capture the latest changes or to make small updates to maintain the site.

Review cycles and timing

The FinOps Foundation’s core operating members maintain the organization as a business. Its technical components, however, must be reviewed and voted upon by a greater group of community members. These meetings are scheduled throughout the month and the timeliness of reviewing commits and changes will vary depending on when these meetings occur.

Issues and small changes like link fixes and typos might occur immediately, as those don’t require a significant amount of code review, voting, and/or approval.


Other ways to get involved:

Working Groups and Special Interest Groups