[Feature] Collaboration suite integration strategy #220

New Issue

2026-07-07T21:16:34+02:00

zemion commented

2026-07-07 21:16:34 +02:00

Define how GovOPlaN integrates collaborative document editing, chat/messaging, video conferencing, project management, and related activity streams.

Source: docs/GOVERNMENT_OPERATIONS_VISION.md

Acceptance criteria:

connector-first strategy is documented for Collabora/OnlyOffice/Nextcloud, Matrix/Mattermost/Rocket.Chat, Jitsi/BigBlueButton, OpenProject, and similar tools
native behavior is justified only when GovOPlaN must own semantics, permissions, audit, retention, or configuration fragments
appointment/workflow/case handoff points are identified
minimum viable connector tests are listed
module boundaries between DMS, connectors, workflow, tasks, appointments, and calendar are clear

Define how GovOPlaN integrates collaborative document editing, chat/messaging, video conferencing, project management, and related activity streams. Source: `docs/GOVERNMENT_OPERATIONS_VISION.md` Acceptance criteria: - connector-first strategy is documented for Collabora/OnlyOffice/Nextcloud, Matrix/Mattermost/Rocket.Chat, Jitsi/BigBlueButton, OpenProject, and similar tools - native behavior is justified only when GovOPlaN must own semantics, permissions, audit, retention, or configuration fragments - appointment/workflow/case handoff points are identified - minimum viable connector tests are listed - module boundaries between DMS, connectors, workflow, tasks, appointments, and calendar are clear

zemion added the area/api codex/ready module/core

labels 2026-07-29 14:15:12 +02:00

zemion commented

2026-07-29 14:28:33 +02:00

Integration strategy refinement

The general maturity ladder (discover, link, search, read, publish, synchronize, migrate, replace) and initial OpenProject/Znuny-OTRS/Zammad/MediaWiki-BlueSpice work are now recorded in govoplan-connectors#11. This collaboration issue should reuse that connector/runtime model rather than define a second integration stack.

## Integration strategy refinement The general maturity ladder (`discover`, `link`, `search`, `read`, `publish`, `synchronize`, `migrate`, `replace`) and initial OpenProject/Znuny-OTRS/Zammad/MediaWiki-BlueSpice work are now recorded in [govoplan-connectors#11](https://git.add-ideas.de/GovOPlaN/govoplan-connectors/issues/11). This collaboration issue should reuse that connector/runtime model rather than define a second integration stack.

zemion commented

2026-08-19 23:15:51 +02:00

Completed in 51bf14f.

The canonical public-sector integration strategy now defines:

connector-first postures for Collabora Online, OnlyOffice, Nextcloud Office/Talk, Matrix, Mattermost, Rocket.Chat, Jitsi, BigBlueButton, OpenProject, and cross-suite activity streams;
the narrow reasons for native behavior: GovOPlaN-owned semantic state, authorization, audit evidence, retention/legal hold, or configuration fragments;
explicit ownership boundaries across DMS, Files, Connectors, Cases, Workflow, Tasks, Appointments, Calendar, Records, and Audit;
four concrete hand-off sequences for conference booking, collaborative documents, chat rooms/threads, and project/work-package synchronization;
common security/recovery/optional-module tests plus provider-focused minimum proofs for office editing, chat, conferencing, and OpenProject.

The document explicitly distinguishes this strategy/test contract from claims of implemented connectors; implementation maturity remains in the owning Connector catalogue and issues.

Verification: git diff --check, Ruff, the full Core backend suite (580 tests, 3 expected skips), and the full production WebUI build/bundle budget all pass.

Completed in `51bf14f`. The canonical public-sector integration strategy now defines: - connector-first postures for Collabora Online, OnlyOffice, Nextcloud Office/Talk, Matrix, Mattermost, Rocket.Chat, Jitsi, BigBlueButton, OpenProject, and cross-suite activity streams; - the narrow reasons for native behavior: GovOPlaN-owned semantic state, authorization, audit evidence, retention/legal hold, or configuration fragments; - explicit ownership boundaries across DMS, Files, Connectors, Cases, Workflow, Tasks, Appointments, Calendar, Records, and Audit; - four concrete hand-off sequences for conference booking, collaborative documents, chat rooms/threads, and project/work-package synchronization; - common security/recovery/optional-module tests plus provider-focused minimum proofs for office editing, chat, conferencing, and OpenProject. The document explicitly distinguishes this strategy/test contract from claims of implemented connectors; implementation maturity remains in the owning Connector catalogue and issues. Verification: `git diff --check`, Ruff, the full Core backend suite (580 tests, 3 expected skips), and the full production WebUI build/bundle budget all pass.

zemion closed this issue

2026-08-19 23:15:51 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-core#220