generated from finos/standards-project-blueprint
-
Notifications
You must be signed in to change notification settings - Fork 34
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Initial Draft of the Delivery WG Charter (#167)
Signed-off-by: Eddie Knight <knight@linux.com> Co-authored-by: Eddie Knight <knight@linux.com>
- Loading branch information
1 parent
08692fc
commit a8baa5a
Showing
1 changed file
with
84 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,84 @@ | ||
| # 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](#mission) | ||
| 2. [Approach & Responsibilities](#approach--responsibilities) | ||
| - [Output / Deliverables](#output--deliverables) | ||
| 3. [Out of Scope](#out-of-scope) | ||
| 4. [Meeting Cadence](#meeting-cadence) | ||
| 5. [Governance](#governance) | ||
| - [Membership](#membership) | ||
| - [Changes](#changes) | ||
| - [Meeting Cadence](#meeting-cadence) | ||
| - [Changes](#changes) | ||
|
|
||
| ## 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 eachother, 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 [WG]s 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 [recommendations] 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 <ccc-delivery@lists.finos.org> 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. | ||
|
|
||
| [WG]: <../../community-groups.md#working-groups> | ||
| [SC]: <../../community-groups.md#steering-committee> | ||
| [policies]: <../../community-policies/README.md> | ||
| [recommendations]: <../../community-recommendations/README.md> | ||
| [Communications WG]: <../communications/charter.md> | ||
| [Community Structure WG]: <../communications/charter.md> |