From 9bbb3e4c25b3660e37fc305bc511928862c62205 Mon Sep 17 00:00:00 2001 From: rgriffiths-scottlogic <142981896+rgriffiths-scottlogic@users.noreply.github.com> Date: Fri, 19 Apr 2024 15:24:25 +0100 Subject: [PATCH 01/12] Create Charter-Taxonomy.md First draft of a charter for the Taxonomy working group --- .../working-groups/Charter-Taxonomy.md | 62 +++++++++++++++++++ 1 file changed, 62 insertions(+) create mode 100644 docs/governance/working-groups/Charter-Taxonomy.md diff --git a/docs/governance/working-groups/Charter-Taxonomy.md b/docs/governance/working-groups/Charter-Taxonomy.md new file mode 100644 index 00000000..9e8618db --- /dev/null +++ b/docs/governance/working-groups/Charter-Taxonomy.md @@ -0,0 +1,62 @@ +# Project Charter - FINOS CCC Taxonomy Working Group + +## Mission + +The mission of the FINOS CCC Taxonomy Working Group is to support the aims and ambitions of the FINOS CCC project by creating the taxonomy for the cloud services offered by the cloud hyperscalers. + +## Scope + +The scope of the project is limited to creating a set of files which capture the offerings for various cloud service offerings in a cloud-agnostic way that focuses on the business value of the service offering rather than its technical implementation. For example, in the case of storage offerings, the taxonomy definition would attempt to capture features that are important to the design of an application such as availability and durability of the storage rather than the actual implementation of the underlying storage offering. + +The scope of the project and the prioritization of effort will be guided and shaped by its contributor members. + +## Success Criteria + +* Taxonomy files can be used by others + +## Deliverables + +* One Markdown file per service + +## Participation + +* Open to all participants + +## Roles and Responsibilities + +The working group should self-select which of its contributors should have various roles and/or responsibilities assigned to them, e.g., Maintainer or Approver. + +## Licensing + +* We should use FINOS standard words here + +## Intellectual Property Claims + +* We should use FINOS standard words here + +## Group Information + +### Technical Leaders + +A list of technical leaders and their roles should be kept current here: + +- Name +- GitHub Handle +- Roles + +### Meetings and Minutes + +- Regular meetings of the Taxonomy working group will be held fortnightly. +- Meeting minutes will be documented and made available to all members for reference and transparency. + +### Mailing List + +- The Taxonomy working group mailing list will serve as the primary communication channel for group discussions, announcements, and coordination. +- All members are encouraged to subscribe to the mailing list to stay informed and participate in discussions. + +### Conference Call Details + +- Fortnightly call to be scheduled +- Ad hoc conference calls will be scheduled as needed for in-depth discussions, decision-making, and updates. +- Details regarding conference call schedules, dial-in numbers, access codes, and meeting agendas will be shared with group members in advance. +- Details are also published on the FINOS CCC GitHub repo From 1e132a5156311d677e4b95603a7b3e90012e9e0c Mon Sep 17 00:00:00 2001 From: rgriffiths-scottlogic <142981896+rgriffiths-scottlogic@users.noreply.github.com> Date: Mon, 22 Apr 2024 12:41:00 +0100 Subject: [PATCH 02/12] Update Charter-Taxonomy.md Added distinction between regular and reporting meetings. --- docs/governance/working-groups/Charter-Taxonomy.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/governance/working-groups/Charter-Taxonomy.md b/docs/governance/working-groups/Charter-Taxonomy.md index 9e8618db..145b6939 100644 --- a/docs/governance/working-groups/Charter-Taxonomy.md +++ b/docs/governance/working-groups/Charter-Taxonomy.md @@ -46,8 +46,10 @@ A list of technical leaders and their roles should be kept current here: ### Meetings and Minutes -- Regular meetings of the Taxonomy working group will be held fortnightly. +- Regular meetings of the Taxonomy working group will be held fortnightly. These will be termed "Taxonomy Working Group Regular Meetings". - Meeting minutes will be documented and made available to all members for reference and transparency. +- A reporting meeting will be held once a month, e.g., first Wednesday of the month, in order to discuss recent progress and future direction with the SteerCo, other working groups, and open to any other stakeholders or interested parties to provide input and/or direction. These will be termed "Taxonomy Working Group Reporting Meetings". + - These meetings could also serve as a collaboration forum and an integration point with other working groups for wider discussion. Additional information pertinent to cross-working-group collaboration can be found in the "improving efficiency" charter. ### Mailing List From 20c5bbf2bd91d0c141391662fefdba164ded4d15 Mon Sep 17 00:00:00 2001 From: Sonali Mendis Date: Tue, 7 May 2024 16:52:47 +0100 Subject: [PATCH 03/12] new taxonomy charter --- .../working-groups/taxonomy/charter.md | 62 +++++++++++++++++++ 1 file changed, 62 insertions(+) create mode 100644 docs/governance/working-groups/taxonomy/charter.md diff --git a/docs/governance/working-groups/taxonomy/charter.md b/docs/governance/working-groups/taxonomy/charter.md new file mode 100644 index 00000000..646ccb33 --- /dev/null +++ b/docs/governance/working-groups/taxonomy/charter.md @@ -0,0 +1,62 @@ +# Common Cloud Control Taxonomy Working Group Charter + +This document outlines the mission, scope, and objectives of the Common Cloud Controls (CCC) Taxonomy [WG]. + +## Mission + +The mission of the Taxonomy [WG] is to define and maintain a comprehensive taxonomy of cloud services offered by the cloud hyperscalers. + +## Objectives / Responsibilities + +- This [WG] is responsible for coming up with the top-level cloud services taxonomy. +- This [WG] is responsible for breaking down each of the top-level taxonomies into more specific sub taxonomies. +- This [WG] is responsible for coming up with common cloud controls (features) for each of the identified taxonomies. +- This [WG] is responsible for coming up with newer versions of existing common cloud controls in timely manner. +- This [WG] is responsible for developing and maintaining set of technical design requirements for each of the identified common cloud controls. + +### Output / Deliverables + +- Top level cloud services taxonomy markdown which will cover the core functionalities provided across all cloud service providers. +- Second level taxonomy markdown for each service taxonomy defined under the top-level taxonomies. +- A taxonomy markdown file per second level taxonomy, which will identify the minimum set of common cloud controls (features) that should be present for a service to be considered portable. +- A feature file per taxonomy markdown, that will contain technical design requirements for features identified under the taxonomy markdown file. + +## Out of Scope + +This [WG] is not responsible to maintaining a list of features provided by different cloud hyperscalers. + +## Approach + +- Will explore into cloud service categorizations done by other FINOS projects when defining the top/secondary level taxonomies +- Propose and agree upon a top level and second level taxonomies as a group. +- Identifying common set of features offered by AWS, Google, and Azure under each of the service taxonomies. +- Document the key features needed to make a architecture portable within cloud providers. +- Document technical design requirements as validation tests per taxonomy. +- Revisit the taxonomies to refine the common cloud controls in a timely manner. +- Maintain open and transparent communication channels for all WG activities and decisions regarding deliverables + +## Membership + +The membership structure of this working group. + +[WG] Lead: Sonali Mendis + +***Note:*** This [WG] adhere to the latest recommendations from the Community Structure working group. See [Community Organization](../recommendations/community-organisation.md#roles-definition-for-a-working-group) + +## Meeting Cadence + +* This working group will use the mail group for regular communications. +* This working group will use biweekly [regular meetings](../community-guidelines/communication.md#regular-meetings) and [ad hoc meetings](../community-guidelines/communication.md#ad-hoc-meetings) as required to discuss [WG] specific tasks. +* This working group will use monthly [reporting meetings](../community-guidelines/communication.md#reporting-meetings) and [ad hoc meetings](../community-guidelines/communication.md#ad-hoc-meetings) as required to collaborate with other CCC working groups. +* A member of this working group will represent this working group on for any calls scheduled by the steering committee ([SC]) for participation by the full CCC community, such as quarterly [SC] calls. + +## Governance + +This [WG] will remain compliant with all applicable community policies + +### 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> \ No newline at end of file From e6065bef7e461a87de39655c5d4230b6f3ad3f10 Mon Sep 17 00:00:00 2001 From: Sonali Mendis Date: Tue, 7 May 2024 19:39:36 +0100 Subject: [PATCH 04/12] update to the taxonomy charter links --- docs/governance/working-groups/taxonomy/charter.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/governance/working-groups/taxonomy/charter.md b/docs/governance/working-groups/taxonomy/charter.md index 646ccb33..cb78f7da 100644 --- a/docs/governance/working-groups/taxonomy/charter.md +++ b/docs/governance/working-groups/taxonomy/charter.md @@ -46,8 +46,8 @@ The membership structure of this working group. ## Meeting Cadence * This working group will use the mail group for regular communications. -* This working group will use biweekly [regular meetings](../community-guidelines/communication.md#regular-meetings) and [ad hoc meetings](../community-guidelines/communication.md#ad-hoc-meetings) as required to discuss [WG] specific tasks. -* This working group will use monthly [reporting meetings](../community-guidelines/communication.md#reporting-meetings) and [ad hoc meetings](../community-guidelines/communication.md#ad-hoc-meetings) as required to collaborate with other CCC working groups. +* This working group will use biweekly [regular meetings](../../community-guidelines/communication.md#regular-wg-meetings) and [ad hoc meetings](../../community-guidelines/communication.md#ad-hoc-wg-meetings) as required to discuss [WG] specific tasks. +* This working group will use monthly [SteerCo reporting meetings](../../community-guidelines/communication.md#steerco-reporting-meetings) and [ad hoc meetings](../../community-guidelines/communication.md#ad-hoc-wg-meetings) as required to collaborate with other CCC working groups. * A member of this working group will represent this working group on for any calls scheduled by the steering committee ([SC]) for participation by the full CCC community, such as quarterly [SC] calls. ## Governance From b74af7150d3246fe82ce3073a944f68b23ab26ae Mon Sep 17 00:00:00 2001 From: Eddie Knight Date: Thu, 9 May 2024 00:48:17 -0500 Subject: [PATCH 05/12] revised content Signed-off-by: Eddie Knight --- .../working-groups/Charter-Taxonomy.md | 64 ------------------- .../working-groups/taxonomy/charter.md | 63 +++++++++--------- 2 files changed, 31 insertions(+), 96 deletions(-) delete mode 100644 docs/governance/working-groups/Charter-Taxonomy.md diff --git a/docs/governance/working-groups/Charter-Taxonomy.md b/docs/governance/working-groups/Charter-Taxonomy.md deleted file mode 100644 index 145b6939..00000000 --- a/docs/governance/working-groups/Charter-Taxonomy.md +++ /dev/null @@ -1,64 +0,0 @@ -# Project Charter - FINOS CCC Taxonomy Working Group - -## Mission - -The mission of the FINOS CCC Taxonomy Working Group is to support the aims and ambitions of the FINOS CCC project by creating the taxonomy for the cloud services offered by the cloud hyperscalers. - -## Scope - -The scope of the project is limited to creating a set of files which capture the offerings for various cloud service offerings in a cloud-agnostic way that focuses on the business value of the service offering rather than its technical implementation. For example, in the case of storage offerings, the taxonomy definition would attempt to capture features that are important to the design of an application such as availability and durability of the storage rather than the actual implementation of the underlying storage offering. - -The scope of the project and the prioritization of effort will be guided and shaped by its contributor members. - -## Success Criteria - -* Taxonomy files can be used by others - -## Deliverables - -* One Markdown file per service - -## Participation - -* Open to all participants - -## Roles and Responsibilities - -The working group should self-select which of its contributors should have various roles and/or responsibilities assigned to them, e.g., Maintainer or Approver. - -## Licensing - -* We should use FINOS standard words here - -## Intellectual Property Claims - -* We should use FINOS standard words here - -## Group Information - -### Technical Leaders - -A list of technical leaders and their roles should be kept current here: - -- Name -- GitHub Handle -- Roles - -### Meetings and Minutes - -- Regular meetings of the Taxonomy working group will be held fortnightly. These will be termed "Taxonomy Working Group Regular Meetings". -- Meeting minutes will be documented and made available to all members for reference and transparency. -- A reporting meeting will be held once a month, e.g., first Wednesday of the month, in order to discuss recent progress and future direction with the SteerCo, other working groups, and open to any other stakeholders or interested parties to provide input and/or direction. These will be termed "Taxonomy Working Group Reporting Meetings". - - These meetings could also serve as a collaboration forum and an integration point with other working groups for wider discussion. Additional information pertinent to cross-working-group collaboration can be found in the "improving efficiency" charter. - -### Mailing List - -- The Taxonomy working group mailing list will serve as the primary communication channel for group discussions, announcements, and coordination. -- All members are encouraged to subscribe to the mailing list to stay informed and participate in discussions. - -### Conference Call Details - -- Fortnightly call to be scheduled -- Ad hoc conference calls will be scheduled as needed for in-depth discussions, decision-making, and updates. -- Details regarding conference call schedules, dial-in numbers, access codes, and meeting agendas will be shared with group members in advance. -- Details are also published on the FINOS CCC GitHub repo diff --git a/docs/governance/working-groups/taxonomy/charter.md b/docs/governance/working-groups/taxonomy/charter.md index cb78f7da..819914d9 100644 --- a/docs/governance/working-groups/taxonomy/charter.md +++ b/docs/governance/working-groups/taxonomy/charter.md @@ -8,55 +8,54 @@ The mission of the Taxonomy [WG] is to define and maintain a comprehensive taxon ## Objectives / Responsibilities -- This [WG] is responsible for coming up with the top-level cloud services taxonomy. -- This [WG] is responsible for breaking down each of the top-level taxonomies into more specific sub taxonomies. -- This [WG] is responsible for coming up with common cloud controls (features) for each of the identified taxonomies. -- This [WG] is responsible for coming up with newer versions of existing common cloud controls in timely manner. -- This [WG] is responsible for developing and maintaining set of technical design requirements for each of the identified common cloud controls. +- Identify common cloud service categories, prioritizing those most commonly used within financial service institutions +- Create and maintain an index of all common service categories each organized by common categorical delineations +- Create and maintain a list of descriptions for the minimum viable features of each service category +- Create and maintain an asset describing the ways to test the presence of each feature for a service +- Ensure all artifacts comply with requirements documented by the [Delivery WG] prior to release +- Collaborate with [Delivery WG] to publish each release on the agreed schedule +- Collaborate with the [Communications WG] to incorporate user feedback into the development cycle ### Output / Deliverables -- Top level cloud services taxonomy markdown which will cover the core functionalities provided across all cloud service providers. -- Second level taxonomy markdown for each service taxonomy defined under the top-level taxonomies. -- A taxonomy markdown file per second level taxonomy, which will identify the minimum set of common cloud controls (features) that should be present for a service to be considered portable. -- A feature file per taxonomy markdown, that will contain technical design requirements for features identified under the taxonomy markdown file. +The following artifacts will be created and stored in the project GitHub repo: -## Out of Scope - -This [WG] is not responsible to maintaining a list of features provided by different cloud hyperscalers. +- Index of common service categories +- List of feature descriptions for each service in the index +- Test descriptions for each feature on each service -## Approach +## Out of Scope -- Will explore into cloud service categorizations done by other FINOS projects when defining the top/secondary level taxonomies -- Propose and agree upon a top level and second level taxonomies as a group. -- Identifying common set of features offered by AWS, Google, and Azure under each of the service taxonomies. -- Document the key features needed to make a architecture portable within cloud providers. -- Document technical design requirements as validation tests per taxonomy. -- Revisit the taxonomies to refine the common cloud controls in a timely manner. -- Maintain open and transparent communication channels for all WG activities and decisions regarding deliverables +The following activities will not be performed by this group: -## Membership +- Working on assets related to cybersecurity topics +- Public-facing communications -The membership structure of this working group. +## Governance -[WG] Lead: Sonali Mendis +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]. -***Note:*** This [WG] adhere to the latest recommendations from the Community Structure working group. See [Community Organization](../recommendations/community-organisation.md#roles-definition-for-a-working-group) +### Membership -## Meeting Cadence +The membership structure of this working group. -* This working group will use the mail group for regular communications. -* This working group will use biweekly [regular meetings](../../community-guidelines/communication.md#regular-wg-meetings) and [ad hoc meetings](../../community-guidelines/communication.md#ad-hoc-wg-meetings) as required to discuss [WG] specific tasks. -* This working group will use monthly [SteerCo reporting meetings](../../community-guidelines/communication.md#steerco-reporting-meetings) and [ad hoc meetings](../../community-guidelines/communication.md#ad-hoc-wg-meetings) as required to collaborate with other CCC working groups. -* A member of this working group will represent this working group on for any calls scheduled by the steering committee ([SC]) for participation by the full CCC community, such as quarterly [SC] calls. +- WG Lead: Sonali Mendis +- SC Sponsor: Robert Griffiths +- This group is not authorized to create independent sub-groups. -## Governance +### Meeting Cadence -This [WG] will remain compliant with all applicable community policies +- This working group will use the mail group for regular communications. +- This group will host a public meeting via the FINOS calendar no less than once every three (3) weeks, excluding November and December. +- The WG Lead or their delegate must present verbal or written updates to the [SC] at its regular public meetings. ### 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> \ No newline at end of file +[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> From f9c69e42535723cb7af1eb93b26cb15a10546653 Mon Sep 17 00:00:00 2001 From: rgriffiths-scottlogic <142981896+rgriffiths-scottlogic@users.noreply.github.com> Date: Thu, 9 May 2024 13:26:11 +0100 Subject: [PATCH 06/12] Update charter.md Ensure that tracking of vendor support of taxonomy features created by [WG] is out of scope --- docs/governance/working-groups/taxonomy/charter.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/governance/working-groups/taxonomy/charter.md b/docs/governance/working-groups/taxonomy/charter.md index 819914d9..cc1bec97 100644 --- a/docs/governance/working-groups/taxonomy/charter.md +++ b/docs/governance/working-groups/taxonomy/charter.md @@ -30,6 +30,7 @@ The following activities will not be performed by this group: - Working on assets related to cybersecurity topics - Public-facing communications +- Tracking cloud vendor support of taxonomy features ## Governance From a007a869eb48f976f457c281ad7a0a86f7830ecd Mon Sep 17 00:00:00 2001 From: Sonali Mendis Date: Fri, 10 May 2024 14:25:30 +0100 Subject: [PATCH 07/12] updated the format and the meeting cadence --- .../working-groups/taxonomy/charter.md | 30 ++++++++++++++----- 1 file changed, 23 insertions(+), 7 deletions(-) diff --git a/docs/governance/working-groups/taxonomy/charter.md b/docs/governance/working-groups/taxonomy/charter.md index cc1bec97..32e6053c 100644 --- a/docs/governance/working-groups/taxonomy/charter.md +++ b/docs/governance/working-groups/taxonomy/charter.md @@ -1,4 +1,4 @@ -# Common Cloud Control Taxonomy Working Group Charter +# Taxonomy Working Group Charter This document outlines the mission, scope, and objectives of the Common Cloud Controls (CCC) Taxonomy [WG]. @@ -6,7 +6,20 @@ This document outlines the mission, scope, and objectives of the Common Cloud Co The mission of the Taxonomy [WG] is to define and maintain a comprehensive taxonomy of cloud services offered by the cloud hyperscalers. -## Objectives / Responsibilities +## 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) + +## Approach & Responsibilities - Identify common cloud service categories, prioritizing those most commonly used within financial service institutions - Create and maintain an index of all common service categories each organized by common categorical delineations @@ -40,14 +53,17 @@ This [WG] will remain compliant with all applicable community [policies]. At the The membership structure of this working group. -- WG Lead: Sonali Mendis -- SC Sponsor: Robert Griffiths +- **WG Lead:** Sonali Mendis +- **SC Sponsor:** Robert Griffiths + +### Sub-Groups + - This group is not authorized to create independent sub-groups. -### Meeting Cadence +### Meeting & Communication - This working group will use the mail group for regular communications. -- This group will host a public meeting via the FINOS calendar no less than once every three (3) weeks, excluding November and December. +- This group will host a recurring WG meeting (not hosted by FINOS) every two weeks, with possible exceptions for months, April, November and December. - The WG Lead or their delegate must present verbal or written updates to the [SC] at its regular public meetings. ### Changes @@ -59,4 +75,4 @@ Any functional changes to this charter must be approved through a majority vote [policies]: <../../community-policies/README.md> [recommendations]: <../../community-recommendations/README.md> [Communications WG]: <../communications/charter.md> -[Community Structure WG]: <../communications/charter.md> +[Community Structure WG]: <../communications/charter.md> \ No newline at end of file From e17a1350bab8b9c7db8c2cc555d3b788ef55415a Mon Sep 17 00:00:00 2001 From: Sonali Mendis Date: Fri, 10 May 2024 14:29:25 +0100 Subject: [PATCH 08/12] update --- .../working-groups/taxonomy/charter.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/governance/working-groups/taxonomy/charter.md b/docs/governance/working-groups/taxonomy/charter.md index 32e6053c..6edf06ed 100644 --- a/docs/governance/working-groups/taxonomy/charter.md +++ b/docs/governance/working-groups/taxonomy/charter.md @@ -2,22 +2,22 @@ This document outlines the mission, scope, and objectives of the Common Cloud Controls (CCC) Taxonomy [WG]. -## Mission - -The mission of the Taxonomy [WG] is to define and maintain a comprehensive taxonomy of cloud services offered by the cloud hyperscalers. - ## 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) +4. [Governance](#governance) - [Membership](#membership) + - [Sub-Groups](#sub-groups) + - [Meeting & Communication](#meeting--communication) - [Changes](#changes) - - [Meeting Cadence](#meeting-cadence) - - [Changes](#changes) + +## Mission + +The mission of the Taxonomy [WG] is to define and maintain a comprehensive taxonomy of cloud services offered by the cloud hyperscalers. + ## Approach & Responsibilities From 6bd8a59e8d7a50900f9387d80e0960dc9388fa5b Mon Sep 17 00:00:00 2001 From: Eddie Knight Date: Sun, 12 May 2024 21:24:21 -0500 Subject: [PATCH 09/12] Added community feedback Signed-off-by: Eddie Knight --- docs/governance/working-groups/taxonomy/charter.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/governance/working-groups/taxonomy/charter.md b/docs/governance/working-groups/taxonomy/charter.md index 6edf06ed..197052ea 100644 --- a/docs/governance/working-groups/taxonomy/charter.md +++ b/docs/governance/working-groups/taxonomy/charter.md @@ -16,8 +16,7 @@ This document outlines the mission, scope, and objectives of the Common Cloud Co ## Mission -The mission of the Taxonomy [WG] is to define and maintain a comprehensive taxonomy of cloud services offered by the cloud hyperscalers. - +The mission of the Taxonomy [WG] is to define and maintain a comprehensive taxonomy of cloud services offered by the cloud hyperscalers. This initiative aims to establish a standardized nomenclature and attributes for common cloud capabilities such as VMs, Storage, and Networking. By creating this uniform taxonomy, the WG will facilitate the application of a set of controls across various cloud provider implementations, addressing common risks and promoting broader applicability of the CCC project's resources. ## Approach & Responsibilities From cd6ccce559a4bfbcfd33f979f6ff3380260f7b5f Mon Sep 17 00:00:00 2001 From: Sonali Mendis Date: Mon, 13 May 2024 10:58:15 +0100 Subject: [PATCH 10/12] review comments addressed --- docs/governance/working-groups/taxonomy/charter.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/governance/working-groups/taxonomy/charter.md b/docs/governance/working-groups/taxonomy/charter.md index 197052ea..d909847c 100644 --- a/docs/governance/working-groups/taxonomy/charter.md +++ b/docs/governance/working-groups/taxonomy/charter.md @@ -42,7 +42,7 @@ The following activities will not be performed by this group: - Working on assets related to cybersecurity topics - Public-facing communications -- Tracking cloud vendor support of taxonomy features +- Tracking cloud vendor support of service features ## Governance @@ -62,7 +62,7 @@ The membership structure of this working group. ### Meeting & Communication - This working group will use the mail group for regular communications. -- This group will host a recurring WG meeting (not hosted by FINOS) every two weeks, with possible exceptions for months, April, November and December. +- This group will host a recurring WG meeting (not hosted by FINOS) every two weeks, with possible interferences on global holidays. - The WG Lead or their delegate must present verbal or written updates to the [SC] at its regular public meetings. ### Changes From 4ab87b73413eec0cda49abe3480bf6ea96db73f9 Mon Sep 17 00:00:00 2001 From: Eddie Knight Date: Mon, 13 May 2024 13:55:37 -0500 Subject: [PATCH 11/12] Changed meeting cadence phrasing to 'informal' Signed-off-by: Eddie Knight --- docs/governance/working-groups/taxonomy/charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/governance/working-groups/taxonomy/charter.md b/docs/governance/working-groups/taxonomy/charter.md index d909847c..f4c60f2b 100644 --- a/docs/governance/working-groups/taxonomy/charter.md +++ b/docs/governance/working-groups/taxonomy/charter.md @@ -62,7 +62,7 @@ The membership structure of this working group. ### Meeting & Communication - This working group will use the mail group for regular communications. -- This group will host a recurring WG meeting (not hosted by FINOS) every two weeks, with possible interferences on global holidays. +- This group will host an informal recurring WG meeting every two weeks, with possible interferences on global holidays. - The WG Lead or their delegate must present verbal or written updates to the [SC] at its regular public meetings. ### Changes From bc109c0d5a7a2cac926274f5762d2879ac7df72d Mon Sep 17 00:00:00 2001 From: Eddie Knight Date: Thu, 16 May 2024 07:56:11 -0500 Subject: [PATCH 12/12] Non-functional language change Co-authored-by: Adrian Hammond --- docs/governance/working-groups/taxonomy/charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/governance/working-groups/taxonomy/charter.md b/docs/governance/working-groups/taxonomy/charter.md index f4c60f2b..925203b0 100644 --- a/docs/governance/working-groups/taxonomy/charter.md +++ b/docs/governance/working-groups/taxonomy/charter.md @@ -16,7 +16,7 @@ This document outlines the mission, scope, and objectives of the Common Cloud Co ## Mission -The mission of the Taxonomy [WG] is to define and maintain a comprehensive taxonomy of cloud services offered by the cloud hyperscalers. This initiative aims to establish a standardized nomenclature and attributes for common cloud capabilities such as VMs, Storage, and Networking. By creating this uniform taxonomy, the WG will facilitate the application of a set of controls across various cloud provider implementations, addressing common risks and promoting broader applicability of the CCC project's resources. +The mission of the Taxonomy [WG] is to define and maintain a comprehensive taxonomy of service(s) offered by the cloud hyperscalers. This initiative aims to establish a standardized nomenclature and attributes for common service categories such as VMs, Storage, and Networking. By creating this uniform taxonomy, the WG will facilitate the application of a set of controls across various cloud provider implementations, addressing common risks and promoting broader applicability of the CCC project's resources. ## Approach & Responsibilities