Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Metric: Change Request Closure Ratio #187

Closed
5 of 7 tasks
geekygirldawn opened this issue Mar 2, 2023 · 6 comments
Closed
5 of 7 tasks

New Metric: Change Request Closure Ratio #187

geekygirldawn opened this issue Mar 2, 2023 · 6 comments

Comments

@geekygirldawn
Copy link
Member

geekygirldawn commented Mar 2, 2023

This issue is created to collect comments on the Change Request Closure metric. Note: This was renamed from "Keeping up with Change Requests"

This metric can be found here: Google Doc

CHAOSS Metric Quality Checklist

This checklist is used for new metrics to ensure we follow CHAOSS quality standards and processes.

Process

  • Add the new metric to release notes issue in working group repo
  • Update the Metrics Spreadsheet to indicate that the metric is under community review.

When above steps are completed:

Content Quality

  • Required headings are filled in
  • If any, ensure links to other CHAOSS metrics work
  • Optional headings that have no content are removed
  • Contributors section lists those contributors that want to be named
  • The name of the metric is the same in all locations

Technical Requirements

  • Message that the metric will be part of the next regular release is at top of page:

This metric is a release candidate. To comment on this metric please see Issue [#[put the respective Issue Number here]](URL to issue). Following a comment period, this metric will be included in the next regular release.

  • Metric file name is the full metric name and only contains lower case letters and hyphens (“-”) for spaces
  • Images are included using markdown and absolute links (as described in the metrics template)
  • Images have at least one empty line above and below them
  • Ensure images are placed in image folder and followed naming convention
  • Ensure tables within metric are converted as images and placed in the image folder (both original MD and screenshotted PNG format) and follow the naming convention
  • No HTML code in the metrics markdown.
@eyehwan
Copy link
Member

eyehwan commented Mar 2, 2023

Seeing that you are still typing on the doc, so I will take a look tomorrow. :)

@geekygirldawn
Copy link
Member Author

@germonprez Can we add this to the Common WG agenda for discussion today? I'm still working on it now, but should have something ready to discuss by the meeting time :)

@eyehwan - thanks! It should be ready for you to review by your morning tomorrow.

@germonprez
Copy link
Contributor

Certainly! I'll make sure it is on the agenda.

@geekygirldawn geekygirldawn changed the title New Metric: Keeping up with Change Requests New Metric: Change Request Closure Ratio Mar 2, 2023
@geekygirldawn
Copy link
Member Author

@germonprez @ElizabethN @klumb - thanks for all of your feedback today. I've reworked this to be a ratio metric and would love to have you do another pass at it with more feedback!

@eyehwan I'd appreciate your feedback, too!

@geekygirldawn
Copy link
Member Author

I've moved the metric from the gdoc to PR #188

@ElizabethN
Copy link
Member

Closing this as it seems to have been resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants