Audit API/DB/ImapDB split
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 175
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Lots of things in ImapDB aren't really IMAP specfic, and mean it's not so easy to plug in a "purelocal" server version
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 the API/DB/ImapDB split and a possible purelocal server version, but it does not identify files, tests, or a specific change. Start by mapping the current ImapDB responsibilities and their callers; done means the non-IMAP-specific responsibilities have a clear home and the purelocal version can be assessed against that split.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- backend-api-design, databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100