This document outlines the mission, scope, and objectives of the Common Cloud Controls (CCC) Communications WG
The mission of the WG is to develop communications frameworks to identify problems within the CCC community, organize resolution efforts, and communicate solutions and benefits.
This group will:
- Maintain a public-facing explanation of the problem this project addresses, the solutions it provides, and the value created by those solutions
- Maintain and distribute a user-feedback mechanism for all project outputs
- Parse and publish user feedback for project consideration
- Maintain a project roadmap detailing upcoming user-impacting changes planned by each WG
- Communicate any roadmap changes to users and stakeholders
- Communicate all information regarding project releases provided by the Delivery WG
- When applicable, publicly communicate how user feedback has been integrated into a project release
The following items will be maintained in the project repository:
- Public-facing Project Roadmap
- Marketing collateral such as graphics and website code
- Community engagement guides
- De-personalized end-user requirements and requests (through GitHub issues)
- Determining the priority or relevance of a feature request
- Spontaneous inquiries from the community, ranging from implementation specifics to interactions on social media platforms
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.
The membership structure of this working group:
- WG Lead: Alex St. Pierre
- SteerCo Sponsor: Eddie Knight
- This group is not authorized to create independent sub-groups.
- This WG will use the mail group [email protected] for routine communications.
- A formal bi-weekly meeting will be created on the FINOS community calendar as a space to gather end-user feedback, address community inquiries, and act as an entry point for new contributors.
- A group member should represent this WG on any calls scheduled by the SC for participation by the full CCC project community.
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.