Bugs time estimation
Open
help wanted
priority-2
starter
- Dominant language
- HTML
- Stars
- 79
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
MD file needs guidance on when bugs should and shouldn't be time estimated
Contributor guide
No contributing guide indexed for this repository
Research direction
Find the relevant Markdown page in the process handbook and read its existing guidance for estimating work. Add clear guidance on when bugs should and should not receive time estimates; done means the distinction is documented for contributors and maintainers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100