Skip to content

charter.md

Latest commit

 

History

History
67 lines (41 loc) · 2.5 KB

charter.md

File metadata and controls

67 lines (41 loc) · 2.5 KB

<NAME_OF_WORKING_GROUP> Charter

This document outlines the mission, scope, and objectives of the Common Cloud Controls (CCC) <name of the working group>.

Table of Contents

  1. Mission
  2. Approach & Responsibilities
  3. Out of Scope
  4. Governance

Mission

<The mission of the working group and its high level role within the CCC project.>

Approach & Responsibilities

This group will:

  • <A list detailing how this group will work, and things this group will be responsible for.>

Output / Deliverables

The following artifacts will be created and stored in the project GitHub repo:

  • <A list of outputs / deliverables the working group should produce.>

Out of Scope

The following activities will not be performed by this group:

  • <An explicit list of the items that do not fall within in the scope of this group's responsibility.>

Governance

This WG will remain compliant with all applicable community policies. At the guidance of the WG Lead, this group will seek to implement guidelines set forth by the Community Structure WG.

Membership

The membership structure of this working group:

  • WG Lead: <name of the WG lead>
  • SC Sponsor: <name of the SteerCo member who sponsored formation or continuation of this group>

Sub-Groups

  • This group <is or is not> authorized to create independent sub-groups. <Any additional details>

Meetings & Communication

  • This working group will use the mail group <ccc-[wg-name]@lists.finos.org> for regular communications.
  • <Specify the types of meetings this working group will have in order to discuss the working group specific matters and their frequency>.
  • <Specify the types of meetings this working group will have to collaborate with other CCC working groups and their frequency>.
  • A group member should represent this WG on any calls scheduled by the SC for participation by the full CCC project community.

Changes

Any functional changes to this charter must be approved through a majority vote by the SC. Minor changes such as formatting may be merged upon approval from any SC member.