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

[Feature] Define scheduling module boundary for Terminfindung and meeting-time polls #1

New Issue
Closed
opened 2026-07-07 02:18:42 +02:00 by zemion · 3 comments
zemion commented 2026-07-07 02:18:42 +02:00
Owner
Copy Link

Context

GovOPlaN Scheduling owns Terminfindung and meeting-time coordination: scheduling polls, availability collection, candidate-slot ranking, invitations/reminders, and handoff into calendar or appointment booking modules.

This module should stay separate from:

  • govoplan-calendar: calendar sync, calendar views, event import/export, free/busy adapters.
  • govoplan-appointments: bookable public service appointments, queues, resources, and confirmed appointment lifecycle.

Acceptance Criteria

  • Define Scheduling ownership separate from Calendar and Appointments.
  • Decide internal-only, external/public, or both for scheduling polls.
  • Define participant availability, privacy, retention, and audit events.
  • Define capability contracts with Calendar, Access/IDM, Mail/Notifications, Portal, Appointments, Workflow/Tasks.
  • Decide first package scaffold: backend-only, WebUI-only, or both.

Initial Integration Notes

  • Calendar should remain the source for free/busy and finalized event placement.
  • Mail/Notifications should send invites, reminders, changes, and poll result messages.
  • Portal may expose external/public participation links.
  • Access/IDM should govern organizer permissions and internal identity lookup.
<!-- codex-scheduling-bootstrap:module-boundary-20260707 --> ## Context GovOPlaN Scheduling owns Terminfindung and meeting-time coordination: scheduling polls, availability collection, candidate-slot ranking, invitations/reminders, and handoff into calendar or appointment booking modules. This module should stay separate from: - `govoplan-calendar`: calendar sync, calendar views, event import/export, free/busy adapters. - `govoplan-appointments`: bookable public service appointments, queues, resources, and confirmed appointment lifecycle. ## Acceptance Criteria - [ ] Define Scheduling ownership separate from Calendar and Appointments. - [ ] Decide internal-only, external/public, or both for scheduling polls. - [ ] Define participant availability, privacy, retention, and audit events. - [ ] Define capability contracts with Calendar, Access/IDM, Mail/Notifications, Portal, Appointments, Workflow/Tasks. - [ ] Decide first package scaffold: backend-only, WebUI-only, or both. ## Initial Integration Notes - Calendar should remain the source for free/busy and finalized event placement. - Mail/Notifications should send invites, reminders, changes, and poll result messages. - Portal may expose external/public participation links. - Access/IDM should govern organizer permissions and internal identity lookup.
zemion added this to the Module And Integration Roadmap milestone 2026-07-07 02:18:42 +02:00
zemion added the
type
feature
priority
p2
status
triage
module/scheduling
 labels 2026-07-08 00:54:12 +02:00
zemion added the
codex/ready
 label 2026-07-08 03:06:28 +02:00
zemion commented 2026-07-09 11:55:52 +02:00
Author
Owner
Copy Link

Resolved by the expanded scheduling README.

Updated README.md with scheduling ownership separate from calendar and appointments, internal/external/public poll decision, participant availability privacy/retention/audit expectations, capability contracts with calendar/access/IDM/mail/notifications/portal/appointments/workflow/tasks, and the first package scaffold decision. Synced to the repository wiki.

Resolved by the expanded scheduling README. Updated `README.md` with scheduling ownership separate from calendar and appointments, internal/external/public poll decision, participant availability privacy/retention/audit expectations, capability contracts with calendar/access/IDM/mail/notifications/portal/appointments/workflow/tasks, and the first package scaffold decision. Synced to the repository wiki.
zemion commented 2026-07-14 20:08:44 +02:00
Author
Owner
Copy Link

User Notes To Reconcile With This Issue

The following reminders should be checked against the current implementation and issue scope. Mark each as implemented, still open, or obsolete:

  • Check terminplaner.dfn.de, Doodle, and similar tools as UX/reference behavior.
  • Select days and timeslots.
  • Allow yes / no / maybe answers.
  • Allow or disallow multiple answers.
  • Select participants, internal and external.
  • Alternatively share a public link; this should work without access, with limited functionality.
  • For internal participants, check calendars for collisions when calendar is present/enabled.
  • Block out timeslots in the organizer's calendar(s).
  • Wait for participant answers.
  • Send reminders to participants who have not answered yet.
  • Decide on the final option.
  • Send out VEVENT once decided.
  • Free alternative blockers and create/update the final calendar event.

This comment is a reminder/audit list, not a request to duplicate existing implemented work. The next pass should compare it with the current govoplan-scheduling state and close or split remaining work.

## User Notes To Reconcile With This Issue The following reminders should be checked against the current implementation and issue scope. Mark each as implemented, still open, or obsolete: - Check `terminplaner.dfn.de`, Doodle, and similar tools as UX/reference behavior. - Select days and timeslots. - Allow yes / no / maybe answers. - Allow or disallow multiple answers. - Select participants, internal and external. - Alternatively share a public link; this should work without access, with limited functionality. - For internal participants, check calendars for collisions when calendar is present/enabled. - Block out timeslots in the organizer's calendar(s). - Wait for participant answers. - Send reminders to participants who have not answered yet. - Decide on the final option. - Send out VEVENT once decided. - Free alternative blockers and create/update the final calendar event. This comment is a reminder/audit list, not a request to duplicate existing implemented work. The next pass should compare it with the current `govoplan-scheduling` state and close or split remaining work.
zemion commented 2026-07-14 20:09:36 +02:00
Author
Owner
Copy Link

Codex note: follow-up audit issue created as govoplan-scheduling#3 so the reminder checklist remains actionable while this closed boundary issue stays historical.

Codex note: follow-up audit issue created as `govoplan-scheduling#3` so the reminder checklist remains actionable while this closed boundary issue stays historical.
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/scheduling
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-scheduling#1
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?