add-ideas/govoplan-calendar
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

[Feature] Add CalDAV protocol sync, recurrence expansion, and free/busy capability #3

New Issue
Open
opened 2026-07-07 02:52:07 +02:00 by zemion · 3 comments
zemion commented 2026-07-07 02:52:07 +02:00
Owner
Copy Link

Context

The first govoplan-calendar module stores VEVENT/iCalendar data and preserves raw iCalendar properties, but it is not yet a full CalDAV protocol implementation and does not yet expand every recurrence form for availability queries.

Acceptance Criteria

  • Implement recurrence expansion for RRULE, RDATE, EXDATE, RECURRENCE-ID, overridden instances, and detached instances.
  • Add a free/busy capability for scheduling, appointments, resource checks, and groupware adapters.
  • Define CalDAV collection sync tokens, ETags, REPORT handling, and conflict handling.
  • Add import/export/sync tests with multi-instance recurring events and exceptions.
  • Keep protocol adapters optional so core-only and calendar-only startup do not require Open-Xchange or connector packages.

Related Context

  • Wiki: Repo-docs-CALENDAR-INTEGRATION-CONCEPT
  • Boundary issue: add-ideas/govoplan-calendar#1
  • Open-Xchange adapter issue: add-ideas/govoplan-calendar#2

Folded Sync Refactor Guardrails From #13

The provider-specific complexity debt from govoplan-calendar#13 is part of the broader sync/CalDAV implementation work and should be addressed incrementally while this issue changes sync behavior.

Additional acceptance notes:

  • Split provider-specific sync/parsing code into focused CalDAV, ICS, Graph, and EWS service modules before adding substantially more sync behavior.
  • Add parser fixtures for each provider before refactoring complex parser paths.
  • Keep the public calendar service API stable for existing module consumers.
  • Prioritize simplifying parse_discovery_multistatus, event_to_component, graph_event_payload, parse_ews_calendar_items, discover_caldav_calendars, sync_graph_source, and update_event as sync features are touched.

Source: folded from govoplan-calendar#13 (source/security-audit, audit complexity baseline codex-audit-full-2026-07-11:calendar-complexity-baseline).

<!-- codex-calendar-followup:caldav-recurrence-freebusy-20260707 --> ## Context The first `govoplan-calendar` module stores VEVENT/iCalendar data and preserves raw iCalendar properties, but it is not yet a full CalDAV protocol implementation and does not yet expand every recurrence form for availability queries. ## Acceptance Criteria - [ ] Implement recurrence expansion for RRULE, RDATE, EXDATE, RECURRENCE-ID, overridden instances, and detached instances. - [ ] Add a free/busy capability for scheduling, appointments, resource checks, and groupware adapters. - [ ] Define CalDAV collection sync tokens, ETags, REPORT handling, and conflict handling. - [ ] Add import/export/sync tests with multi-instance recurring events and exceptions. - [ ] Keep protocol adapters optional so core-only and calendar-only startup do not require Open-Xchange or connector packages. ## Related Context - Wiki: `Repo-docs-CALENDAR-INTEGRATION-CONCEPT` - Boundary issue: `add-ideas/govoplan-calendar#1` - Open-Xchange adapter issue: `add-ideas/govoplan-calendar#2` ## Folded Sync Refactor Guardrails From #13 The provider-specific complexity debt from `govoplan-calendar#13` is part of the broader sync/CalDAV implementation work and should be addressed incrementally while this issue changes sync behavior. Additional acceptance notes: - Split provider-specific sync/parsing code into focused CalDAV, ICS, Graph, and EWS service modules before adding substantially more sync behavior. - Add parser fixtures for each provider before refactoring complex parser paths. - Keep the public calendar service API stable for existing module consumers. - Prioritize simplifying `parse_discovery_multistatus`, `event_to_component`, `graph_event_payload`, `parse_ews_calendar_items`, `discover_caldav_calendars`, `sync_graph_source`, and `update_event` as sync features are touched. Source: folded from `govoplan-calendar#13` (`source/security-audit`, audit complexity baseline `codex-audit-full-2026-07-11:calendar-complexity-baseline`).
zemion added this to the Module And Integration Roadmap milestone 2026-07-07 02:52:07 +02:00
zemion commented 2026-07-07 14:50:47 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • A first backend recurrence expansion primitive now exists in govoplan_calendar.backend.ical for RRULE/RDATE/EXDATE over a requested range.
  • This does not yet expose CalDAV, free/busy, or recurrence-expanded event listing endpoints; those remain the main scope of this issue.

Changed Files

  • src/govoplan_calendar/backend/ical.py
  • tests/test_ical.py

Verification

  • PYTHONPATH=/mnt/DATA/git/govoplan-calendar/src:/mnt/DATA/git/govoplan-tenancy/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-core/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest discover -s /mnt/DATA/git/govoplan-calendar/tests

Next / Blocked

  • Design API endpoints for expanded occurrences and free/busy before adding CalDAV protocol handlers.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - A first backend recurrence expansion primitive now exists in govoplan_calendar.backend.ical for RRULE/RDATE/EXDATE over a requested range. - This does not yet expose CalDAV, free/busy, or recurrence-expanded event listing endpoints; those remain the main scope of this issue. ### Changed Files - `src/govoplan_calendar/backend/ical.py` - `tests/test_ical.py` ### Verification - `PYTHONPATH=/mnt/DATA/git/govoplan-calendar/src:/mnt/DATA/git/govoplan-tenancy/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-core/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest discover -s /mnt/DATA/git/govoplan-calendar/tests` ### Next / Blocked - Design API endpoints for expanded occurrences and free/busy before adding CalDAV protocol handlers. Suggested status label: `status/in-progress`
zemion commented 2026-07-07 15:30:43 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • Implemented a calendar-owned CalDAV sync source model with collection URL, auth metadata, sync token, ctag, last sync status, and no persisted secrets.
  • Added a standard-library CalDAV client for PROPFIND, calendar-query full sync, sync-collection incremental sync, GET fallback, multistatus parsing, ETags, deleted resources, and sync tokens.
  • Added inbound sync service that imports all VEVENT components in a CalDAV resource, preserves raw ICS, updates source_href/etag metadata, and soft-deletes local events for remote deletions.
  • Exposed CalDAV source CRUD and manual sync endpoints under /calendar/caldav/sources.
  • Remaining work: credential-store integration, scheduled/background sync, outbound writes/conflict policy, full free/busy API, and user-facing recurrence editing.

Changed Files

  • README.md
  • docs/CALENDAR_INTEGRATION_CONCEPT.md
  • src/govoplan_calendar/backend/caldav.py
  • src/govoplan_calendar/backend/db/models.py
  • src/govoplan_calendar/backend/ical.py
  • src/govoplan_calendar/backend/manifest.py
  • src/govoplan_calendar/backend/migrations/versions/8d9e0f1a2b3c_caldav_sync_sources.py
  • src/govoplan_calendar/backend/router.py
  • src/govoplan_calendar/backend/schemas.py
  • src/govoplan_calendar/backend/service.py
  • tests/test_caldav.py
  • tests/test_ical.py

Verification

  • PYTHONPATH=/mnt/DATA/git/govoplan-calendar/src:/mnt/DATA/git/govoplan-tenancy/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-core/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest discover -s /mnt/DATA/git/govoplan-calendar/tests
  • PYTHONPATH=/mnt/DATA/git/govoplan-calendar/src:/mnt/DATA/git/govoplan-tenancy/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-core/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m compileall -q /mnt/DATA/git/govoplan-calendar/src/govoplan_calendar /mnt/DATA/git/govoplan-calendar/tests
  • cd /mnt/DATA/git/govoplan-core && ./.venv/bin/python -m govoplan_core.devserver --smoke --no-reload

Next / Blocked

  • Add credential-store/connector profile integration before enabling scheduled CalDAV sync.
  • Define outbound write and conflict resolution policy for local edits to synced CalDAV events.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Implemented a calendar-owned CalDAV sync source model with collection URL, auth metadata, sync token, ctag, last sync status, and no persisted secrets. - Added a standard-library CalDAV client for PROPFIND, calendar-query full sync, sync-collection incremental sync, GET fallback, multistatus parsing, ETags, deleted resources, and sync tokens. - Added inbound sync service that imports all VEVENT components in a CalDAV resource, preserves raw ICS, updates source_href/etag metadata, and soft-deletes local events for remote deletions. - Exposed CalDAV source CRUD and manual sync endpoints under /calendar/caldav/sources. - Remaining work: credential-store integration, scheduled/background sync, outbound writes/conflict policy, full free/busy API, and user-facing recurrence editing. ### Changed Files - `README.md` - `docs/CALENDAR_INTEGRATION_CONCEPT.md` - `src/govoplan_calendar/backend/caldav.py` - `src/govoplan_calendar/backend/db/models.py` - `src/govoplan_calendar/backend/ical.py` - `src/govoplan_calendar/backend/manifest.py` - `src/govoplan_calendar/backend/migrations/versions/8d9e0f1a2b3c_caldav_sync_sources.py` - `src/govoplan_calendar/backend/router.py` - `src/govoplan_calendar/backend/schemas.py` - `src/govoplan_calendar/backend/service.py` - `tests/test_caldav.py` - `tests/test_ical.py` ### Verification - `PYTHONPATH=/mnt/DATA/git/govoplan-calendar/src:/mnt/DATA/git/govoplan-tenancy/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-core/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest discover -s /mnt/DATA/git/govoplan-calendar/tests` - `PYTHONPATH=/mnt/DATA/git/govoplan-calendar/src:/mnt/DATA/git/govoplan-tenancy/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-core/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m compileall -q /mnt/DATA/git/govoplan-calendar/src/govoplan_calendar /mnt/DATA/git/govoplan-calendar/tests` - `cd /mnt/DATA/git/govoplan-core && ./.venv/bin/python -m govoplan_core.devserver --smoke --no-reload` ### Next / Blocked - Add credential-store/connector profile integration before enabling scheduled CalDAV sync. - Define outbound write and conflict resolution policy for local edits to synced CalDAV events. Suggested status label: `status/in-progress`
zemion commented 2026-07-07 15:48:53 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • Implemented encrypted CalDAV credential references, env secret refs, source sync scheduling fields, and due-sync service/API/task entry points.
  • Implemented two-way CalDAV PUT/DELETE for local event create/update/delete with ETag preconditions and multi-VEVENT resource preservation.
  • Added backend free/busy API primitive with recurrence expansion for scheduling and appointment integrations.

Changed Files

  • src/govoplan_calendar/backend/caldav.py
  • src/govoplan_calendar/backend/service.py
  • src/govoplan_calendar/backend/db/models.py
  • src/govoplan_calendar/backend/migrations/versions/9e0f1a2b3c4d_caldav_credentials_outbound_sync.py
  • src/govoplan_calendar/backend/tasks.py
  • tests/test_caldav.py

Verification

  • python -m unittest discover -s /mnt/DATA/git/govoplan-calendar/tests: 18 tests OK
  • python -m compileall -q src/govoplan_calendar tests: OK
  • govoplan_core.devserver --smoke --no-reload: OK

Next / Blocked

  • Remaining follow-ups: UI for CalDAV source/credential/sync settings, CalDAV server endpoints if GovOPlaN should be a CalDAV server, and richer user-facing recurrence editing.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Implemented encrypted CalDAV credential references, env secret refs, source sync scheduling fields, and due-sync service/API/task entry points. - Implemented two-way CalDAV PUT/DELETE for local event create/update/delete with ETag preconditions and multi-VEVENT resource preservation. - Added backend free/busy API primitive with recurrence expansion for scheduling and appointment integrations. ### Changed Files - `src/govoplan_calendar/backend/caldav.py` - `src/govoplan_calendar/backend/service.py` - `src/govoplan_calendar/backend/db/models.py` - `src/govoplan_calendar/backend/migrations/versions/9e0f1a2b3c4d_caldav_credentials_outbound_sync.py` - `src/govoplan_calendar/backend/tasks.py` - `tests/test_caldav.py` ### Verification - `python -m unittest discover -s /mnt/DATA/git/govoplan-calendar/tests: 18 tests OK` - `python -m compileall -q src/govoplan_calendar tests: OK` - `govoplan_core.devserver --smoke --no-reload: OK` ### Next / Blocked - Remaining follow-ups: UI for CalDAV source/credential/sync settings, CalDAV server endpoints if GovOPlaN should be a CalDAV server, and richer user-facing recurrence editing. Suggested status label: `status/in-progress`
zemion added the
type
feature
priority
p2
status
triage
module/calendar
codex/ready
 labels 2026-07-07 22:44:30 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
HTTP API contracts, routers, schemas, or API smoke behavior.
area/auth
Authentication, sessions, access bootstrap, or login behavior.
area/db
Database sessions, models, transactions, or persistence primitives.
area/deployment
Deployment, release, operations, or runtime packaging.
area/devex
Local developer workflow, scripts, tests, tooling, or release helpers.
area/docs
Durable documentation and project guidance.
area/governance
Governance policy, audit, privacy, retention, or compliance behavior.
area/marketing
Public website, product messaging, publication copy, or legal page content.
area/migrations
Alembic migrations, schema bootstrap, or persistence evolution.
area/module-system
Module discovery, manifests, capabilities, routing, or optional integrations.
area/rbac
Permissions, roles, delegation, or authorization policy.
area/release
Versioning, release locks, tags, packaging, or dependency pins.
area/security
Security posture, static analysis, supply-chain hardening, or vulnerability remediation.
area/tenancy
Tenant boundaries, provisioning, or tenant-scoped data behavior.
area/webui
Shared WebUI shell, frontend components, routing, or frontend tests.
audit/complexity
Complexity finding from Radon, Xenon, or equivalent maintainability scans.
audit/duplication
Duplicated-code finding from jscpd or equivalent similarity scans.
audit/false-positive
Audit finding reviewed as a narrow false positive or acceptable risk.
audit/needs-design
Audit finding that needs an architectural or product decision before implementation.
audit/quick-fix
Audit finding that appears narrow and directly fixable.
audit/structural
Audit finding that needs design, refactoring, or behavior review.
codex/needs-human
Needs an explicit human decision before Codex should implement.
codex/ready
Suitable for Codex to pick up with the existing issue context.
module/access
GovOPlaN access, identity, authentication, RBAC, and administration behavior.
module/addresses
GovOPlaN Addresses module behavior or integration.
module/admin
GovOPlaN Admin module behavior or integration.
module/appointments
GovOPlaN Appointments module behavior or integration.
module/approvals
GovOPlaN Approvals module behavior or integration.
module/assets
GovOPlaN Assets module behavior or integration.
module/audit
GovOPlaN Audit module behavior or integration.
module/booking
GovOPlaN Booking module behavior or integration.
module/calendar
GovOPlaN Calendar module behavior or integration.
module/campaign
GovOPlaN campaign module behavior or integration.
module/cases
GovOPlaN Cases module behavior or integration.
module/certificates
GovOPlaN Certificates module behavior or integration.
module/committee
GovOPlaN Committee module behavior or integration.
module/connectors
GovOPlaN Connectors module behavior or integration.
module/consultation
GovOPlaN Consultation module behavior or integration.
module/contracts
GovOPlaN Contracts module behavior or integration.
module/core
GovOPlaN core runner, shared primitives, shell, or extension points.
module/dist-lists
GovOPlaN Distribution Lists module behavior or integration.
module/dms
GovOPlaN Dms module behavior or integration.
module/docs
GovOPlaN documentation layer behavior or integration.
module/erp
GovOPlaN Erp module behavior or integration.
module/evaluation
GovOPlaN Evaluation module behavior or integration.
module/facilities
GovOPlaN Facilities module behavior or integration.
module/files
GovOPlaN files module behavior or integration.
module/fit-connect
GovOPlaN Fit Connect module behavior or integration.
module/forms
GovOPlaN Forms module behavior or integration.
module/forms-runtime
GovOPlaN Forms Runtime module behavior or integration.
module/grants
GovOPlaN Grants module behavior or integration.
module/helpdesk
GovOPlaN Helpdesk module behavior or integration.
module/identity
GovOPlaN Identity module behavior or integration.
module/identity-trust
GovOPlaN Identity Trust module behavior or integration.
module/idm
GovOPlaN Idm module behavior or integration.
module/inspections
GovOPlaN Inspections module behavior or integration.
module/issue-reporting
GovOPlaN Issue Reporting module behavior or integration.
module/learning
GovOPlaN Learning module behavior or integration.
module/ledger
GovOPlaN Ledger module behavior or integration.
module/mail
GovOPlaN mail module behavior or integration.
module/notifications
GovOPlaN Notifications module behavior or integration.
module/ops
GovOPlaN Ops module behavior or integration.
module/organizations
GovOPlaN Organizations module behavior or integration.
module/payments
GovOPlaN Payments module behavior or integration.
module/permits
GovOPlaN Permits module behavior or integration.
module/policy
GovOPlaN Policy module behavior or integration.
module/poll
GovOPlaN Poll module behavior or integration.
module/portal
GovOPlaN Portal module behavior or integration.
module/postbox
GovOPlaN Postbox module behavior or integration.
module/procurement
GovOPlaN Procurement module behavior or integration.
module/records
GovOPlaN Records module behavior or integration.
module/reporting
GovOPlaN Reporting module behavior or integration.
module/resources
GovOPlaN Resources module behavior or integration.
module/risk-compliance
GovOPlaN Risk Compliance module behavior or integration.
module/scheduling
GovOPlaN Scheduling module behavior or integration.
module/search
GovOPlaN Search module behavior or integration.
module/tasks
GovOPlaN Tasks module behavior or integration.
module/templates
GovOPlaN Templates module behavior or integration.
module/tenancy
GovOPlaN Tenancy module behavior or integration.
module/transparency
GovOPlaN Transparency module behavior or integration.
module/web
GovOPlaN public website, product page, or publication content.
module/workflow
GovOPlaN Workflow module behavior or integration.
module/xoev
GovOPlaN Xoev module behavior or integration.
module/xrechnung
GovOPlaN Xrechnung module behavior or integration.
module/xta-osci
GovOPlaN Xta Osci module behavior or integration.
priority
p0
Immediate stop-the-line priority.
priority
p1
High priority for the next focused work window.
priority
p2
Normal planned priority.
priority
p3
Low priority or opportunistic cleanup.
source/backlog-import
Imported from markdown backlog, roadmap, plan, or TODO files.
source/module-roadmap
Created from GovOPlaN module and integration roadmap planning.
source/security-audit
Created from a structured security or code-quality audit report.
source/todo-scan
Imported from inline TODO/FIXME/HACK markers by the Gitea TODO importer.
status
blocked
Cannot progress without a decision, dependency, credential, or external change.
status
in-progress
Currently being worked.
status
needs-info
Needs clarifying input before implementation can proceed safely.
status
ready
Ready for implementation.
status
triage
Needs review, ownership, priority, or acceptance criteria.
type
bug
A reproducible defect, regression, or incorrect behavior.
type
debt
Cleanup, refactoring, risk reduction, or deferred engineering work.
type
docs
Documentation, process, or developer workflow work.
type
feature
New user-visible behavior or platform capability.
type
task
Implementation, maintenance, migration, or operational work.
type
user-story
End-to-end user journey or real-world process story used to steer product slices.
No Label
codex/ready
module/calendar
priority
p2
status
triage
type
feature
Milestone
No items
No Milestone Module And Integration Roadmap
Projects
Clear projects
No project
Assignees
Clear assignees
zemion
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-calendar#3
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?