Skip to content

Latest commit

 

History

History
84 lines (58 loc) · 3.9 KB

charter.md

File metadata and controls

84 lines (58 loc) · 3.9 KB
Raw

Delivery Working Group Charter

This document outlines the mission, scope, and objectives of the Common Cloud Controls (CCC) Delivery WG.

Table of Contents

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

Mission

This WG defines and maintains the delivery process for the Common Cloud Controls project deliverables.

The mission of the Delivery WG is to establish and maintain robust communication channels, ensuring openness and clarity in all activities and decisions related to outputs and deliverables. We aim to curate a comprehensive repository of community outputs slated for release, diligently managing version control and devising optimal strategies for content dissemination.

By coordinating with fellow WG's, we endeavor to synchronize release efforts, while meticulously defining and adhering to a structured release schedule, fostering efficiency and coherence in our endeavors.

Approach & Responsibilities

This group will:

  • Maintain open and transparent communication channels for all WG activities and decisions in regard to outputs/deliverables
  • Define and document standards related to how content is organized in the repository
  • Document standards for how all project artifacts reference each other, such as control identifiers
  • Create and maintain automation related to acceptance of content proposed to the project repository
  • Maintain a list of all community outputs that need to be released
  • Determine and document project best practices for versioning and releasing content
  • Maintain a version controlled process for releasing content
  • Collaborate with other WGs to coordinate releases
  • Define and maintain a release strategy and schedule (whether it be biweekly, monthly, etc.)
  • Coordinate with the Communications WG regarding upcoming releases

Output / Deliverables

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

  • Documentation of the project's comprehensive release strategy
  • Documentation of the project's content format and hygiene standards
  • Automation related to the acceptance and management of content proposed to the project repository
  • Automation related to release of version-controlled project artifacts
  • Release artifacts corresponding to any version-controlled outputs from the project

Out of Scope

The following activities will not be performed by this group:

  • Technicial work that does not pertain to a release or repo content format
  • Public-facing communications

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: Damien Burks
  • SC Sponsor: Eddie Knight
  • This group is not authorized to create independent sub-groups.

Meeting Cadence

  • This working group will use the mail group [email protected] for regular communications.
  • 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.