pimutils / pimutils/vdirsyncer
Move read_only to pair section
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 185
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 1
Description
Just like we have read-only storages, I would like to propose the idea of write-only storages. The idea here is that vdirsyncer would keep the data in a write-only storage up-to-date when synced, but would never pull changes from that storage (and would, in fact, destroy any changes made to that storage locally).
The use case would be a storage which is used to display information, but should never be modified by any tool. By making that storage write-only, one ensures that no accidental modifications to the storage will ever make their way back to the canonical copy of the data and, furthermore, that such accidental modifications will be erased and restored back to the canonical data on the next sync.
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
The issue names no files, tests, or entry points. Start by locating the existing read_only storage or pair configuration and its sync-direction handling. Define how the proposed write-only behavior would be configured and verified, then add coverage for keeping the display storage aligned without pulling its local changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100