-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Comments
Seeing that you are still typing on the doc, so I will take a look tomorrow. :) |
@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. |
Certainly! I'll make sure it is on the agenda. |
@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! |
I've moved the metric from the gdoc to PR #188 |
Closing this as it seems to have been resolved. |
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
When above steps are completed:
Content Quality
Technical Requirements
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.
The text was updated successfully, but these errors were encountered: