MetaMask / MetaMask/contributor-docs
Procedures: Issue triage
Open
category-documentation
github-migration-triaged
team-wallet-framework
wf-documentation
- Dominant language
- JavaScript
- Stars
- 86
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Discovering and using issue labels
- Notifying the correct team
- How to assess severity
Contributor guide
Research direction
No file, test, or entry point is named. Start by reviewing the contributor-docs structure and existing issue-triage guidance, then determine where procedures for discovering labels, notifying the correct team, and assessing severity belong. Done means those three topics are documented clearly and consistently with the repository’s existing guides.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100