Method to track inactive/stale users and competitions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 176
- Forks
- 74
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 21
Description
Hi,
I'm wondering if you have a method for tracking or listing inactive/stale users and competitions. This information would help in that we could decide whether or not to remove/clean-up users and competitions that are no longer in use (reducing clutter).
Inactivity (stale) could be determined by custom date ranges for things like:
User Last logon date
Days since user creation if user never logged on
Competition last submission date
Days since competition creation if no submissions
Potentially this could also apply to datasets, bundles, etc too.
Contributor guide
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
No files, tests, or entry points are named. Start by reviewing how users, competitions, datasets, and bundles record creation, login, and submission activity, then clarify the scope and date-range behavior with maintainers. Done should include an agreed way to list stale resources and criteria for each resource type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100