Code-dot-mil / Code-dot-mil/code.mil
Suggestion: use labels sparingly
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 144
- PR merge metrics
- No merged PRs in 30d
Description
Look at other popular and widely-used projects on GitHub, such as https://github.com/openssl/OpenSSL.git and https://github.com/OpenSC/OpenSC.git
Both have tons of issues to process, but an issue would have maybe one, at most two labels. Here I see it rare for an issue to have less than *four* labels, usually five or six.
Please reconsider, and stop throwing every possibly-remotely-applicable label at an issue - it's both confusing and annoying to the viewer. Pick one that's the closest, and stay with it.
My $0.02.
Contributor guide
Research direction
Review the repository's current issue-label usage and compare it with the OpenSSL and OpenSC examples linked in the issue. Done means agreeing on a smaller labeling policy and applying it consistently, but no implementation files or tests are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100