Code-dot-mil / Code-dot-mil/code.mil
Suggestion: use labels sparingly
Open
[issue-type] question
- 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
Assessment
This issue has not been assessed yet.