feat(dashboard): VEVENTs (meetings) alongside VTODOs #4

Open
opened 2026-05-20 13:35:58 +00:00 by mAi · 0 comments
Collaborator

Carried over from the mgmt.msbls.de teardown plan §3 Gap 1.

Gap

The /dashboard Tasks card surfaces VTODOs only. The mgmt cockpit (now slated for teardown) also surfaces VEVENTs from the same Work+Plan calendars, ordered by start-time, with location + categories. "Meetings today" is a real feature projax doesn't yet replicate.

Once this lands, the last functional reason to keep mgmt.msbls.de alive disappears and the §4 teardown sequence can run end-to-end.

Scope

Small. The CalDAV client already lists VEVENTs (caldav.ListVEVENTs); the dashboard handler needs either:

  • a fourth card (Today's meetings), or
  • a merged Today's schedule card that combines VTODOs + VEVENTs ordered by due/start-time.

Sort: chronological — overdue VTODOs first, then today's events by start, then no-due VTODOs at the end.

Reuse the existing 4-worker pool the Tasks card uses (don't hammer the DAV server). Same 60s TTL cache as the rest of the dashboard.

Out of scope

  • Week / quarter VEVENT views — mgmt never shipped these either, parked indefinitely.
  • Writeback on VEVENTs (the cmd/projax CalDAV writeback path is VTODO-only).
  • RRULE expansion — render single occurrences only.

References

  • Teardown plan §3 Gap 1: docs/plans/mgmt-teardown.md on mai/knuth/phase-3k-mgmt-survey.
  • Original superseded design: m/msbls.de#5 (closed).
  • CalDAV client: caldav/caldav.goListVEVENTs already exists.
Carried over from the [mgmt.msbls.de teardown plan](https://mgit.msbls.de/m/projax/src/branch/mai/knuth/phase-3k-mgmt-survey/docs/plans/mgmt-teardown.md) §3 Gap 1. ## Gap The `/dashboard` Tasks card surfaces VTODOs only. The mgmt cockpit (now slated for teardown) also surfaces VEVENTs from the same `Work`+`Plan` calendars, ordered by start-time, with location + categories. "Meetings today" is a real feature projax doesn't yet replicate. Once this lands, the last functional reason to keep mgmt.msbls.de alive disappears and the §4 teardown sequence can run end-to-end. ## Scope Small. The CalDAV client already lists VEVENTs (`caldav.ListVEVENTs`); the dashboard handler needs either: - a fourth card (`Today's meetings`), or - a merged `Today's schedule` card that combines VTODOs + VEVENTs ordered by due/start-time. Sort: chronological — overdue VTODOs first, then today's events by start, then no-due VTODOs at the end. Reuse the existing 4-worker pool the Tasks card uses (don't hammer the DAV server). Same 60s TTL cache as the rest of the dashboard. ## Out of scope - Week / quarter VEVENT views — mgmt never shipped these either, parked indefinitely. - Writeback on VEVENTs (the `cmd/projax` CalDAV writeback path is VTODO-only). - RRULE expansion — render single occurrences only. ## References - Teardown plan §3 Gap 1: `docs/plans/mgmt-teardown.md` on `mai/knuth/phase-3k-mgmt-survey`. - Original superseded design: `m/msbls.de#5` (closed). - CalDAV client: `caldav/caldav.go` — `ListVEVENTs` already exists.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: m/projax#4
No description provided.