[Feature] Add CardDAV integration after address book model exists #31

Open
opened 2026-07-06 11:25:03 +02:00 by zemion · 1 comment
Owner

Imported from the consolidated GovOPlaN product backlog.

  • Source: /mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/backlog.md
  • Line: 191
  • Section: Milestones > Milestone 11 - Address Book, Templates, And Adoption Polish
  • Source status: PARTIAL.

Imported backlog item:

- [ ] Add CardDAV integration after address book model exists.
<!-- codex-backlog-fingerprint:2d7e143b8a92c5a6ef23cf82 --> Imported from the consolidated GovOPlaN product backlog. - Source: `/mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/backlog.md` - Line: `191` - Section: `Milestones > Milestone 11 - Address Book, Templates, And Adoption Polish` - Source status: `PARTIAL.` Imported backlog item: ```markdown - [ ] Add CardDAV integration after address book model exists. ```
zemion added this to the Milestone 11 - Address Book, Templates, And Adoption Polish milestone 2026-07-06 13:16:58 +02:00
Author
Owner

Codex State: note

Summary

  • CardDAV belongs to the address module after the local vCard model and sync-state model exist.
  • Address-side CardDAV work is tracked in govoplan-addresses#7.
  • Shared connector diagnostics/dry-run contracts are tracked in govoplan-connectors#8.
  • Campaign should only consume the resulting address-source capability; that is tracked in #55.
## Codex State: note ### Summary - CardDAV belongs to the address module after the local vCard model and sync-state model exist. - Address-side CardDAV work is tracked in `govoplan-addresses#7`. - Shared connector diagnostics/dry-run contracts are tracked in `govoplan-connectors#8`. - Campaign should only consume the resulting address-source capability; that is tracked in #55.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-campaign#31
No description provided.