You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As in the other Issues metrics, there are specific instructions for implementing this metric in GrimoireLab, so we should verify these are accurate or remove them to keep from having to check this in the future. Also, no mention of Augur.
The objectives section could use some work
There are parameters which seem like filters to me
Synonyms are in "Data Collection Strategies" and not the Description section
Do we need references?
This is one of our more heavily referenced metrics, so we should make sure it's ✨
Checklist
Process
Create the “revising metric” labeled issue in the authoring WG’s repo for comments during review period
Create pull request of revised metric to WG’s repo (after checking Content Quality and Technical Requirements below)
Add the metric revision to release notes issue in working group repo
Update the Metrics Spreadsheet to indicate that the revised metric is under review
Create issue in CHAOSS/Translations repository to kick-off translation to other languages (please use the the translation issue template)
"Metric Candidate Release" label added to the metric release candidate issue when fully ready fo release
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 and can be done as a collective of all revised metrics from the CHAOSS community.
Content Quality (check all that apply)
Date of last review has been added to the revised metric at the bottom of the markdown file (month/year)
Name of the Metric Being Revised
Issues Closed
Link to Original Metric Release Issue
chaoss/wg-evolution#288
Specific Metric Details that Require Attention
Checklist
Process
When above steps are completed:
Content Quality (check all that apply)
Technical Requirements for any Revisions
The text was updated successfully, but these errors were encountered: