[Epic] Integrate, migrate from, and selectively replace established public-sector tools #11

Open
opened 2026-07-29 14:27:58 +02:00 by zemion · 1 comment
Owner

Outcome

GovOPlaN can coexist tightly with established systems, migrate from them incrementally, and provide native alternatives without requiring a risky big-bang replacement. Initial reference families are OpenProject, Znuny/OTRS-compatible service desks, Zammad, and MediaWiki/BlueSpice.

Integration maturity model

Every connector declares the levels it actually supports: discover, link, search, read, publish, synchronize, migrate, and replace. The UI and documentation must not imply a higher level than the configured connector provides.

Boundaries

  • Connectors owns profiles, credentials references, health, external-reference mappings, polling/webhook diagnostics, and capability declarations.
  • Domain modules own project, case, task, knowledge, workflow, attachment, and policy semantics.
  • Search indexes permitted external references/content through Search contracts.
  • Tabular acquisition flows through Connectors -> Datasources -> Dataflow rather than bypassing governance.

Acceptance criteria

  • The catalogue records protocol/product/version, supported maturity levels, directionality, object mappings, auth, rate limits, and health.
  • Stable external-reference DTOs support deep links, snapshots, provenance, conflict state, and migration identity.
  • Dry-run and bounded import/export expose unsupported fields and lossy mappings before writes.
  • Sync has explicit source-of-truth, conflict, deletion, retry, idempotency, and outcome-unknown policies.
  • Configuration packages can require connector capabilities while optional modules remain optional.
  • The first end-to-end profile is OpenProject; service-desk and knowledge connectors reuse the same runtime contracts.

Related existing work: govoplan-core#187, govoplan-core#220, govoplan-connectors#7, and the OpenProject/public-sector catalogue concept documents.

## Outcome GovOPlaN can coexist tightly with established systems, migrate from them incrementally, and provide native alternatives without requiring a risky big-bang replacement. Initial reference families are OpenProject, Znuny/OTRS-compatible service desks, Zammad, and MediaWiki/BlueSpice. ## Integration maturity model Every connector declares the levels it actually supports: `discover`, `link`, `search`, `read`, `publish`, `synchronize`, `migrate`, and `replace`. The UI and documentation must not imply a higher level than the configured connector provides. ## Boundaries - Connectors owns profiles, credentials references, health, external-reference mappings, polling/webhook diagnostics, and capability declarations. - Domain modules own project, case, task, knowledge, workflow, attachment, and policy semantics. - Search indexes permitted external references/content through Search contracts. - Tabular acquisition flows through Connectors -> Datasources -> Dataflow rather than bypassing governance. ## Acceptance criteria - The catalogue records protocol/product/version, supported maturity levels, directionality, object mappings, auth, rate limits, and health. - Stable external-reference DTOs support deep links, snapshots, provenance, conflict state, and migration identity. - Dry-run and bounded import/export expose unsupported fields and lossy mappings before writes. - Sync has explicit source-of-truth, conflict, deletion, retry, idempotency, and outcome-unknown policies. - Configuration packages can require connector capabilities while optional modules remain optional. - The first end-to-end profile is OpenProject; service-desk and knowledge connectors reuse the same runtime contracts. Related existing work: `govoplan-core#187`, `govoplan-core#220`, `govoplan-connectors#7`, and the OpenProject/public-sector catalogue concept documents.
Author
Owner

Codex State: progress

Summary

  • Pushed the canonical external-reference DTO and discover/link/search/read/publish/synchronize/migrate/replace maturity model in govoplan-core@d9b5708.
  • Created child work packages #12 OpenProject, #13 Znuny/OTRS, and #14 MediaWiki/BlueSpice; native ownership is now Projects, Tickets/Cases, and Wiki respectively.

Next / Blocked

  • Implement the connector catalogue/runtime fields against the shared contract, then take #12 first.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Pushed the canonical external-reference DTO and discover/link/search/read/publish/synchronize/migrate/replace maturity model in govoplan-core@d9b5708. - Created child work packages #12 OpenProject, #13 Znuny/OTRS, and #14 MediaWiki/BlueSpice; native ownership is now Projects, Tickets/Cases, and Wiki respectively. ### Next / Blocked - Implement the connector catalogue/runtime fields against the shared contract, then take #12 first. Suggested status label: `status/in-progress`
zemion added
status
in-progress
and removed
status
ready
labels 2026-07-29 15:54:02 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-connectors#11