microsoft / microsoft/OSSGadget
Project health clarification
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 371
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
I've noticed that some projects have 0.0% for issues or security.
Is this due to a lack of historical data in which to determine health? If so, then what would be an alternative way to display this info as the lack of evidence seems to imply a project is doing poorly which is not the case. And likewise, a lack of evidence should not necessarily be justification to make the project look good either.
Thoughts?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points, so first clarify with maintainers how the issues and security health values are calculated and displayed. Agree on how missing evidence should be represented, then define and validate the chosen behavior against both projects with and without historical data.
Written by the indexing model from the issue text.
Assessment
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100