Skip to content

Commit

Permalink
Board/council updates (#1159)
Browse files Browse the repository at this point in the history
  • Loading branch information
flanakin authored Nov 27, 2024
1 parent 079a0db commit af75322
Show file tree
Hide file tree
Showing 2 changed files with 24 additions and 21 deletions.
20 changes: 11 additions & 9 deletions docs-wiki/Advisory-council.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@ The council is responsible for the following high-level areas:
- **Recognition**: Acknowledging and celebrating the contributions of community members to encourage continued engagement and contribution.

Council members are also expected to facilitate [[Support escalations]] by:

- Reviewing new and unresolved issues and discussions related to their tool or resource at least once per week.
- Responding to issues and discussions about their tool or resource within 2 business days.
- Responding to Microsoft Support escalations within 2 business days.
Expand Down Expand Up @@ -55,21 +56,22 @@ The advisory council consists of the following representative seats:
- Customer Success Unit - CCX
- Customer Success Unit - Infrastructure
- Customer Success Unit - Data & AI
- Azure Customer Experience - FastTrack
- Azure Customer Experience - ISV & Digital Natives
- Commerce - FastTrack
- Developer Relations
- Customer Support Services
- Any FinOps Certified Professional (no limit on number)

This currently includes the following people:

| Seat | Member |
|------|--------|
| Azure Optimization Engine | Helder Pinto |
| Cost optimization workbook | Seif Bassem |
| FinOps hubs | Brett Wilson |
| Governance workbook | Nicolas Teyan |
| PowerShell module | Anthony Romano |
| Learning resources | Fernando Vasconcellos |
| Seat | Member |
| -------------------------- | --------------------- |
| Azure Optimization Engine | Helder Pinto |
| Cost optimization workbook | Seif Bassem |
| FinOps hubs | Brett Wilson |
| Governance workbook | Nicolas Teyan |
| PowerShell module | Anthony Romano |
| Learning resources | Fernando Vasconcellos |

Each seat can be filled by one and only one representative to ensure the council remains fair, balanced, and does not grow too large to be effective. The one exception is FinOps Certified Professionals who we believe have earned the right to contribute independently given their investment in certification and dedication to the FinOps space.

Expand Down
25 changes: 13 additions & 12 deletions docs-wiki/Governing-board.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,7 @@ The board is responsible for identifying short-, medium-, and long-term goals an
- **Compliance**: Ensuring we're in compliance with Microsoft policies and procedures.

Board members are also expected to facilitate [[Support escalations]] by:

- Reviewing new and unresolved issues and discussions at least once per week.
- Responding to Microsoft Support escalations within 2 business days.
- Responding to security investigations within 1 business day.
Expand Down Expand Up @@ -66,18 +67,18 @@ If consensus cannot be reached within 14 days and the board believes the issue i

The governing board consists of the following representative seats:

| Seat | Member |
|------|--------|
| Business sponsor | Nelson Pereira |
| Community | Sonia Cuff |
| Consulting | Manfred Simonis |
| Engineering | Arthur Clares |
| Marketing | Vacant |
| Product | Michael Flanakin |
| FinOps Certified Professional | Vacant |
| Internal customer (one per FinOps persona) | Mark Aggar |
| External customer (one per FinOps persona) | Vacant |
| Advisory Council | Vacant |
| Seat | Member |
| ------------------------------------------ | ---------------- |
| Business sponsor | Nelson Pereira |
| Community | Sonia Cuff |
| Consulting | Manfred Simonis |
| Engineering | Arthur Clares |
| Marketing | Vacant |
| Product | Michael Flanakin |
| FinOps Certified Professional | Vacant |
| Internal customer (one per FinOps persona) | Vacant |
| External customer (one per FinOps persona) | Vacant |
| Advisory Council | Vacant |

Individuals must meet the following criteria in order to attain a board seat:

Expand Down

0 comments on commit af75322

Please sign in to comment.