Metrics Candidate Release Page

Released metrics are only a subset of metric ideas that are being developed. If you would like to learn more and discuss different metrics please visit the working group repositories. Each working group identifies metrics that are candidates for release. The metrics are sorted into Focus Areas. CHAOSS uses a Goal-Question-Metric format to present metrics. Individual metrics are released based on identified goals and questions. The metrics include a detail page with definitions, usecases, and examples.

Important Dates

Release Freeze: June 21st, 2019
Candidate Release: June 24th, 2019
Comments Close: July 24th, 2019
Release Date: August 1st, 2019

Comments about focus areas and associated metrics can be made by following the working group links provided in the release tables and on the associated detail pages. Comments about the format and presentation for the release on the website can be made here. The comment period will remain open for 30 days starting June 24th with and ending July 24th.

Focus Areas by Working Group

Common Metrics WG

Diversity and Inclusion WG

Evolution WG

Risk WG

Value WG

Common Metrics

Common Metrics Repository: https://github.com/chaoss/wg-common

Focus Area - Organizational Affiliation

Goal:
Understand organizational engagement with open source projects.

Metric Question Comment
Organizational Diversity What is the organizational diversity of contributions? Link

Diversity and Inclusion

D&I Repository: https://github.com/chaoss/wg-diversity-inclusion

Focus Area - Event Diversity

Goal:
Identify the diversity and inclusion at events.

Metric Question Comment
Diversity Access Tickets How are Diversity Access Tickets used to support diversity and inclusion for an event? Link
Code of Conduct at Event How does the Code of Conduct for events support diversity and inclusion? Link
Family Friendliness How does enabling families to attend together support diversity and inclusion of the event? Link

Focus Area - Governance

Goal:
Identify how diverse and inclusive our governance is.

Metric Question Comment
Code of Conduct How does the Code of Conduct for the project support diversity and inclusion? Link

Focus Area - Leadership

Goal:
Identify how healthy our community leadership is.

Metric Question Comment
Mentorship How effective are our mentorship programs at supporting diversity and inclusion in our project? Link

Evolution

Evolution Repository: https://github.com/chaoss/wg-evolution

Scope: Aspects related to how the source code changes over time, and the mechanisms that the project has to perform and control those changes.

Focus Area - Code Development

Goal:
Activity - Learn about activity involved in changing (or adding) code.
Question: How many changes are happening to the source code, during a certain time period?

Metric Question Comment
Code Changes What are the number of changes to the source code? Link
Code Changes Lines What are the aggregated number of lines touched in all changes? Link

Question: How many reviews to proposed changes to the source code are happening during a certain time period?

Metric Question Comment
Reviews What are the number of new review requests for changes to the source code? Link
Reviews Accepted How many reviews result in accepting the code change? Link
Reviews Declined What are the number of reviews for changes to the source code that ended declining the change? Link

Question: How many issues related to the source code are happening during a certain time period?

Metric Question Comment
Issues New What are the number of new issues related to the source code? Link
Issues Active What are the number of issues related to the source code that showed some activity during the period? Link
Issues Closed What are the number of issues related to the source code that were closed? Link

Goal:
Efficiency - Learn how effective new code is merged into the code base.
Question: How efficient is the project in reviewing proposed changes to the code, during a certain time period?

Metric Question Comment
Reviews Accepted How many reviews result in accepting the code change? Link
Review Duration How long are proposed changes reviewed before they are accepted? Link

Risk

Risk Repository: https://github.com/chaoss/wg-risk

Focus Area - Business Risk

Goal:
Understand how active a community exists around/to support a given software package.

Metric Question Comment
Elephant Factor What is the distribution of work in the community? Link
Committers How robust and diverse are the contributors to a community? Link

Focus Area - Code Quality

Goal:
Understand the quality of a given software package.

Metric Question Comment
Test Coverage How well is the code tested? Link

Focus Area - Licensing

Goal:
Understand the potential intellectual property(IP) issues associated with a given software package’s use.

Metric Question Comment
License Count How many different licenses are there? Link
License Coverage How much of the code base has declared licenses? Link
License Declared What are the declared software package licenses? Link

Focus Area - Transparency

Goal:
Understand how transparent a given software package is with respect to dependencies, licensing (?), security processes, etc.

Metric Question Comment
Bill of Materials Does the software package have a standard expression of dependencies, licensing, and security-related issues? Link

Value

Value Repository: https://github.com/chaoss/wg-value

Focus Area - Labor Investment

Goal:
Estimate the labor investment in open source projects.

Metric Question Comment
Labor Investment What was the cost of an organization for its employees to create the counted commits, issues, and pull requests (and other contributions)? Link
Project Velocity What is the development speed for an organization? Link

Focus Area - Living Wage

Goal:
Expanding opportunities for people to make a living wage in open source.

Metric Question Comment
Organizational Users Which organizations are using this project? Link

Copyright © 2019 The Linux Foundation® . All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page. Linux is a registered trademark of Linus Torvalds. Privacy Policy and Terms of Use.