# Roadmap This roadmap is our strategic plan that defines our goal or desired outcome and includes the major milestones that are needed to reach it. ### :notebook\_with\_decorative\_cover: Metrics The CHAOSS Metrics Committee defines implementation-agnostic metrics for assessing open source communities' health and sustainability. The CHAOSS Metrics Committee's goals are to establish implementation-agnostic metrics for measuring community activity, contributions, and health; and optionally produce standardized metric exchange formats, detailed use cases, models, or recommendations to analyze specific issues in the industry/OSS world. [**Know more about metrics**](https://github.com/chaoss/metrics) ### :book: Metric Releases The Working Groups within the CHAOSS are focused on releasing new metrics where metrics are identified and defined using a continuous contribution process. The metrics are officially released biannually following a 30 day comment period. [**Check out the metric release**](https://github.com/chaoss/governance/blob/master/community-handbook/metrics-release.md) ### :man\_technologist: **Software Releases** The software committee within the CHAOS community is focused on producing integrated open source software for analyzing software community development across the metric mechanism. ### :busts\_in\_silhouette: Working Groups The working group aims to bring together experiences measuring common metrics, diversity and inclusion, evolution, risk, and value in open source projects. Its main goal focuses on understanding from a qualitative and quantitative point of view how different things can be measured within the community. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://handbook.chaoss.community/community-handbook/about/roadmap.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.