[user_activity] Optimize the thresholds to detect inactive users
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
@marco-c if you think that the number of bugs is too high, we could increase the threshold for the
ABSENTstatus to reduce the number of bugs.
Yeah, let's start with the same value as activity (so 26 weeks, that is half a year). We can file a follow-up issue to decrease both values in the future.
Originally posted by @marco-c in https://github.com/mozilla/relman-auto-nag/pull/1396#discussion_r871089101
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
Start by locating the user_activity handling and the threshold that assigns the ABSENT status. Confirm how the activity threshold is represented, then update the ABSENT threshold to the agreed 26 weeks and check the relevant tests or validation for inactive-user detection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100