Is mbox size field actually needed?
- Dominant language
- Python
- Stars
- 45
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
The mbox size field is populated by the archiver, but not by migrate.py.
It is only ever read by rethread.py, and then only checked for presence.
It does not seem to serve any purpose currently.
Would it ever be needed?
Would it ever be useful as part of a query?
At the very least the purpose of the field needs to be documented.
Contributor guide
No contributing guide indexed for this repository
Research direction
Trace the mbox size field through the archiver, migrate.py, and rethread.py, noting where it is populated, read, and checked for presence. Determine whether it has a current purpose or query value; done means the field's role is documented, or the issue records a clear basis for changing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100