Press Ctrl/Cmd + P to print
or save as PDF

CHAOSS Working Groups

CHAOSS has three types of working groups.

1. Metrics Working Groups

Metrics working groups are responsible for developing and maintaining metrics definitions and metrics models.

Active Working Groups

  • Metrics Development: This working group (formerly known as Common Metrics) focuses on defining the metrics that are used by multiple working groups or are important for community health, but that do not cleanly fit into one of the other existing metrics working groups.

  • Diversity, Equity & Inclusion: This working group aims to bring together experiences measuring diversity, equity and inclusion in open source projects.

  • Metrics-Models: This working group develops models that include the integration of multiple CHAOSS metrics in a way that people would consume them in practice.

Inactive Working Groups

  • Evolution: This working group was focused on refining the metrics that inform evolution and to work with open source software implementations. Future evolution metrics will be defined in the Common WG.

  • Value: This working group was focused on developing metrics that describe value of open source engagement for individuals and organizations. Discussions about value are currently happening in the OSPO WG.

  • Risk: This working group was focused on compliance and risk metrics in Open Source Software. Future evolution metrics will be defined in the Common WG.

2. Context Working Groups

Context WGs are groups of people who share similar contexts related to open source project health. Context WGs are responsible for helping put CHAOSS metrics, metrics models, and software into practice in meaningful ways across varied contexts.

  • OSPO: The OSPO Metrics working group aims to advance how organizations understand the value that open source projects can provide as well as the value of these programs / initiatives. This is a joint effort between the CHAOSS project and the TODO Group.

  • Application Ecosystem: This working group applies CHAOSS metrics in the context of an open-source app ecosystem. The mission of this working group is to build a base set of metrics that is focused on the needs of open source communities that are part of the FOSS app ecosystem.

  • University: The University working group is a joint effort between the CHAOSS project and the OSPO++ community that aims to create a set of recommendations for metrics related to university open source software, particularly as they relate to what might be seen as “success” for university leadership, faculty, students, and staff, keeping in mind that these actors may evaluate success differently.

  • Science: The Science working group aims create a set of recommendations for metrics and models related to scientific open source communities.

3. Operations Working Groups

The Operations Working Groups are supporting the metrics discussions and are responsible for various activities and operations for the CHAOSS project. In the past, many of these efforts were called Initiatives.

  • Communications: The Communications (or Comms) working group focuses on creating outward facing communication and promoting CHAOSS engagement (new contributors, sponsors, metrics users, and CHAOSS software users) to amplify the work being done throughout the CHAOSS community by its contributors.

  • CHAOSScon: The CHAOSScon working group focuses on planning and executing CHAOSS conferences.

  • CHAOSScast: The CHAOSScast working group focuses on managing the CHAOSS podcast.

  • DEI Badging: The DEI Badging working group focuses on our badging initiative that is meant to encourage open source projects and event organizers to obtain our Diversity, Equity, and Inclusion badges for the purposes of leadership self-reflection and self-improvement around the ways that they are centering DEI.

  • Website: The Website working group focus on maintenance of CHAOSS Website.

  • [Design](): Content will be added soon!.

  • [Newcomer Experience](): Content will be added soon!.

Comments and suggestions for this page can be made here: