Created a parent / epic to keep track of this #298

Thanks @eddie-knight , I'll have a look at this today.

Why does this working group exist?

We exist to define and document best practice and process for implementing compliant cloud infrastructure, while streamlining the process for contributions from financial institutions in a frictionless manner.

What are the main, high level objectives this group is working toward?

• (Outputs) Document how to achieve compliance for different infrastructure resources from a financial perspective
• (Inputs) Maintain a knowledge base of up-to-date compliance requirements from member financial institutions

How are each of those objectives being pursued?

• Document opinionated configurations, mitigations, and decisions required to achieve compliance
• Ensure our compliance definitions are informed by industry-wide experience/feedback
• Ensure our communication methods (inputs and outputs) are streamlined to best serve our community and users
• Maintain a list of resources that we want to have documentation/accelerators for
• The SAA template needs to be reviewed and actively maintained by this WG
• EKS, OCP, and Fargate work will be the first items to progress

How is work tracked relating to each of these objectives?

• Github issues on this current repository
• Track issues on the Policy WG project kanban board

What is the best way for a new contributor to begin contributing to this work?

• TODO

Per @abdullahgarcia on the WG call today, the sequence of work will be to establish a MVP approach using EKS, OCP, and Fargate. Developing a process for gathering FI input on policies will come after confirmation from the policy consumers (FIs + Reproducible Infra WG)

Next step is to get this all documented in an easily consumable fashion for both users and contributors. Additional feedback is encouraged on this thread as documentation work continues.