Complete recurrence editing and calendar preferences
This commit is contained in:
@@ -6,7 +6,7 @@
|
||||
|
||||
- calendar collections
|
||||
- VEVENT storage and iCalendar import/export
|
||||
- event recurrence data, recurrence exceptions, and future recurrence expansion
|
||||
- event recurrence data, recurrence expansion, and recurrence exceptions
|
||||
- availability and free/busy semantics
|
||||
- resources such as rooms, shared equipment, and service desks
|
||||
- groupware calendar adapter boundaries, including CalDAV and Open-Xchange
|
||||
@@ -22,7 +22,10 @@ The first standalone module provides:
|
||||
- normalized query fields: start, end, summary, location, all-day flag, status, transparency, classification, calendar ID, UID, recurrence ID, sequence, source, and ETag
|
||||
- iCalendar preservation: raw VEVENT properties, parameters, and generated `text/calendar` export
|
||||
- API endpoints for listing calendars, creating/updating/deleting events, importing iCalendar, and exporting event ICS
|
||||
- free/busy API primitive with recurrence expansion for scheduling and appointment conflict checks
|
||||
- bounded occurrence expansion with RRULE, RDATE, EXDATE, detached overrides,
|
||||
instance/series editing, and free/busy reconciliation
|
||||
- durable per-user calendar view preferences exposed through the platform
|
||||
Settings surface
|
||||
- calendar-owned CalDAV sync sources with credential references, scheduled due-sync metadata, full/incremental inbound sync, two-way PUT/DELETE writes, and ETag conflict handling
|
||||
- a Calendar-owned durable desired-state outbox for two-way CalDAV writes. Event
|
||||
state and the exact external resource snapshot commit atomically; workers use
|
||||
@@ -30,7 +33,10 @@ The first standalone module provides:
|
||||
exponential retry, and semantic GET reconciliation after ambiguous outcomes
|
||||
- WebUI views: month, week, workweek, day, and continuous week-row scrolling
|
||||
|
||||
The first implementation is not yet a full CalDAV network server. It is the internal calendar storage, sync, availability, and UI foundation on which Open-Xchange integration, richer recurrence editing, scheduling inbox/outbox behavior, and CalDAV server endpoints can be built.
|
||||
The implementation is not yet a full CalDAV network server. It is the internal
|
||||
calendar storage, recurrence, sync, availability, and UI foundation on which
|
||||
Open-Xchange integration, scheduling inbox/outbox behavior, and CalDAV server
|
||||
endpoints can be built.
|
||||
|
||||
## Outbound delivery operations
|
||||
|
||||
@@ -197,9 +203,6 @@ The connector boundary should hand calendar a configured profile and credentials
|
||||
|
||||
## Follow-Up Work
|
||||
|
||||
- Full recurrence expansion for RRULE, RDATE, EXDATE, RECURRENCE-ID, overridden instances, and detached instances.
|
||||
- User-facing recurrence editing for RRULE, RDATE, EXDATE, RECURRENCE-ID, overridden instances, and detached instances.
|
||||
- UI management for CalDAV credentials, sync status, sync direction, and conflict resolution.
|
||||
- CalDAV server endpoints if GovOPlaN should expose calendars to external clients rather than only syncing remote collections.
|
||||
- Open-Xchange adapter that maps OX calendars, attendees, resources, recurrence, and free/busy to the internal calendar model.
|
||||
- Attendee RSVP workflow and mail/notification bridge.
|
||||
|
||||
Reference in New Issue
Block a user