New metric: Change Request Commits

[vinodkahuja]

This issue is created to collect comments about the rolling release of Change Request Commits metric

This metric can be found here: https://docs.google.com/document/d/19hWI-j7vCXHUfopw-4-iNWyu5wO0Udg3pf__GLJGnag/edit

See all release candidates: https://chaoss.community/metrics/

CHAOSS Metric Quality Checklist

This checklist is used for new and updated metrics to ensure we follow CHAOSS quality standards and processes. Below checklist items don’t have to be completed all at once: create the metric release candidate issue first and then start working on the checklist.

Process

• [x] Create the “review issue” in the authoring WG’s repo for comments during review period and paste this template in
• [x] Create pull request to edit or add metric to WG’s repo (after checking Content Quality and Technical Requirements below)
• [x] Add the new metric or metric edit to release notes issue in working group repo
• [x] Update the Metrics Spreadsheet
• [x] Create issue in CHAOSS/Translations repository to kick-off translation to other languages (please use the the translation issue template)
• [x] "Metric Candidate Release" label added to the metric release candidate issue.
• [ ] Metric was added to website

When above steps are completed:

• [ ] Announce new/updated metric on mailing list, newsletter, community Zoom call, and Twitter. This can be coordinated with the community manager.

Content Quality

• [x] Required headings are filled in, including Questions.
• [x] Description provides context to metric
• [x] Objectives list sample uses for the metric and desired outcomes
• [x] If any, DEI uses of the metric are included in Objectives
• [x] Optional headings that have no content were removed
• [x] Contributors section lists those contributors that want to be named
• [x] The name of the metric is the same in (1) metric heading, (2) metric file name, (3) focus area, (4) metrics spreadsheet, (5) “review issue”, (6) translation issue, and (7) website

Technical Requirements

• [x] Message in the metric markdown file that the metric will be part of the next regular release is at top of page and the links are correct (this is in the metric template)
• [x] Metric file name is the full metric name and only contains lower case letters and hyphens (“-”) for spaces
• [x] Images are included using markdown and relative links (as described in the metrics template)
• [x] Images have at least one empty line above and below them
• [x] Ensure images are placed in image folder and followed naming convention
• [x] If new focus area is created, ensure focus area is added to wg repo readme and focus area folder readme
• [x] Within the focus area, add the metric in the table and provide the link to the metric and metric question
• [x] Ensure tables within metric are converted as image and placed in the image folder (both original MD and screenshotted PNG format) and follow the naming convention
• [x] No HTML code in the metrics markdown file

[rpaik]

A few questions.

• What's the main goal of this metrics? Is it to show the complexity of the change request or to show diversity?
• If it's for complexity, is it to show the complexity this could be due to the challenging nature of the software or the contributor's inexperience.
• If it's to demonstrate the diversity of contributors in the change request, wouldn't we want to also factor in how many people have provided reviews?

[foundjem]

@rpaik, are your comments still relevant after reading the metric documentation and description? I am curious if we should do more iterations over these practical concerns.

[bhack]

If it's to demonstrate the diversity of contributors in the change request, wouldn't we want to also factor in how many people have provided reviews?

I think that it Is also important to measure the reviewers diversity and approval diversity/fairness (do we have a bias related on who propose the PR and who approve the PR?). This could be also related, when possibile, to the codeowners diversity also If currently we stil don't have a metric about the codeownership coverage and transparency of the repo and the diversity of its gatekeepers. Probably on this topic we could interact more strictly with https://github.com/chaoss/wg-dei/issues/402

[germonprez]

@sgoggins, I"m not sure if this metric is ready for release. Have you had a chance to check out the comments?

[klumb]

The goal of this metric is to measure the number of commits in a PR. As an atomic metric that measures a specific activity, it can inform complexity and diversity however it doesn't measure it. Complexity and Diversity are likely models that could include this metric.

[klumb]

I believe this is ready for release.