Skip to content

caoqianyun/tac

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

29 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

FinOps Technical Advisory Council

The FinOps TAC oversees the FinOps definition, curriculum and technical vision of the FinOps Foundation (https://www.finops.org/about/).

The FinOps TAC is the technical governing body of the FinOps Foundation. TAC outputs are committed into an open source ecosystem to become standardized best practices. It admits and oversees all projects in the FinOps Foundation and has a mandate to facilitate driving neutral consensus for:

  • What is the FinOps definition and capabilities for the industry?
  • What is the open sourced curriculum of the FinOps trainings and certifications?
  • What capabilities are needed to be “FinOps Certified Platform”?
  • What qualifies a service provider to be “FinOps Certified Service Provider”?
  • What KPIs are used to measure quality and success in Cloud Financial Management?
  • What skills do teams need to hire into FinOps roles? What are example jobs descriptions?
  • Managing the FinOps Landscape: https://github.com/finopsfoundation/finops-landscape
  • approving new projects within the scope for FinOps set by the Governing Board (GB)

Voting Members

10 Seats Initially - Mix of Practitioners, GB Appointed, and Premier Members

  1. Mike Fuller, Principal Systems Engineer for FinOps at Atlassian (TAC Chairperson through 12/31/2020)
  2. Ashley Hromatko, Sr. Mgr FinOps at Pearson
  3. Eugene Khvostov, VP Product & Eng at Apptio Cloudability (former AWS Insights)
  4. John McLoughlin, Director Product Management for CloudHealth by VMware
  5. Amitai Rottem, Billing Product Management for Google Cloud (former Microsoft)
  6. Joseph Daly, Director of Cloud Optimization at Nationwide
  7. Antoine Lagier, Contributing Editor and Maintainer of FinOps.world, and French SIG chair
  8. Rich Hoyer, Director of FinOps, SADA
  9. Anders Hagman, Sr Mgr Technology Procurement, Spotify

As defined by the Technical Charter, The Technical Advisory Council (the "TAC") will have ten members determined as follows:

  • three individuals selected by vote of the Governing Board of the FinOps Foundation Fund, a directed fund of the Linux Foundation (the “Directed Fund”);
  • up to three seats for Premier Members of the Directed Fund, with each Premier Member having the right to appoint a representative to the TAC until such point in time as there are more than three Premier Members of the Directed Fund, after which the Premier Members will nominate and elect among themselves three members of the TAC;
  • three individuals that are FinOps Practitioners, as defined in the funding charter of the Directed Fund, selected or elected via a method to be determined by the Governing Board.
  • the remaining number of seats to be filled in a manner as determined by the TAC.

Election schedule

TBD

Meetings and Lists

The TAC will be committed to working in the open on GitHub: https://github.com/finopsfoundation/tac

The TAC meets every other Tuesday at 1pm Pacific Time.

Attendance for voting TAC members is required, please send a proxy along with any updates if you are unable to join. Meetings are open to anyone.

Working Doc and Agenda: https://docs.google.com/document/d/1_gesq-zy3948bwErO4DqVJYmFgL-cAY7Q2oGH4uQ-BI/edit#

TAC emailing list (open to all): https://groups.google.com/a/finops.org/g/tac

Zoom Meeting: https://us02web.zoom.us/j/85763363501

Special Interest Groups (SIGs) & Working Groups (WG)

The TAC will approved the formation of SIGs. Currently, the following Special Interest Groups are being considered:

  • FinOps Capabilities
  • Definitions of Finops and Practitioners
  • FinOps-for-Kubernetes (with a whitepaper delivered at CNC NA)
  • FinOps-for-Finance (for Finance practitioners)
  • FinOps-for-Engineers (for Finance practitioners)
  • Education Committee
  • FinOps-for-AWS
  • FinOps-for-GCP
  • FinOps-for-Azure
  • DIY-FinOps

Releases

No releases published

Packages

No packages published