Consider to nag people on long-time inactive bugs
Open
Nobody has claimed this yet.
area-Backlog
area-Bug Inactivity
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
In order to push people to better maintain their backlogs we should consider to nag people about long-time inactive bugs based on
- their severity and/or priority
- their period of inactivity (where actions from bots should be excluded)
We might start from S1/S2 bugs and rather long inactivity periods to not flood people's inboxes.
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. Start by surveying the repository for existing reminder and bug-processing flows, then define how severity, priority, inactivity, and bot actions are evaluated; done requires an agreed nagging policy and tests covering the initial S1/S2 scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100