From 4bddb6a3480263c373c295460982eab9a2744e70 Mon Sep 17 00:00:00 2001 From: zemion Date: Mon, 6 Jul 2026 22:01:34 +0200 Subject: [PATCH] Sync Repo-docs-GOVOPLAN-MODULE-ROADMAP from project files --- Repo-docs-GOVOPLAN-MODULE-ROADMAP.-.md | 99 +++++++++++++++++--------- 1 file changed, 64 insertions(+), 35 deletions(-) diff --git a/Repo-docs-GOVOPLAN-MODULE-ROADMAP.-.md b/Repo-docs-GOVOPLAN-MODULE-ROADMAP.-.md index d0e0159..b3fecf4 100644 --- a/Repo-docs-GOVOPLAN-MODULE-ROADMAP.-.md +++ b/Repo-docs-GOVOPLAN-MODULE-ROADMAP.-.md @@ -1,4 +1,4 @@ - + > Mirrored from `/mnt/DATA/git/govoplan-core/docs/GOVOPLAN_MODULE_ROADMAP.md`. > Origin: `repository`. @@ -7,46 +7,75 @@ --- # GovOPlaN Module And Integration Roadmap -This page captures module and integration candidates that should be tracked in Gitea issues. It is durable planning context; implementation state, priorities, blockers, and acceptance criteria belong on the linked issues. +This page maps current module and integration ideas to existing GovOPlaN repositories or to missing-module decisions. Issues are the active backlog. This document is durable routing context and should be mirrored to the Gitea wiki. -## Existing Platform Modules +## Current Routing -- `govoplan-tenancy`: tenant table ownership, lifecycle, tenant settings, switching, delete vetoes, and erasure orchestration. -- `govoplan-access`: authentication, accounts, sessions, API keys, groups, memberships, RBAC, principal resolution, and identity integrations; depends on tenancy for tenant records. -- `govoplan-policy`: permission catalogues, hierarchical policy decisions, delegation ceilings, explainability, and simulations. -- `govoplan-audit`: audit log table ownership, audit sink, audit queries, exports, evidence bundles, and compliance traceability. -- `govoplan-admin`: governance template table ownership, administrative shell, and module-contributed admin surfaces. - -## Existing Service And Business Modules - -- `govoplan-files`: managed files, storage spaces, sharing, downloads, metadata, and future document storage boundaries. -- `govoplan-mail`: SMTP/IMAP profiles, credentials, sending, mailbox views, policy, and mail workflow integration. -- `govoplan-campaign`: campaign authoring, validation, review/send control, reports, and recipient-driven communication. +| Idea | Owner | Tracking | +| --- | --- | --- | +| Access as a module | `govoplan-access` | `add-ideas/govoplan-access#7` | +| OpenProject API / project management connector | `govoplan-connectors` | `add-ideas/govoplan-connectors#1` | +| Native project-management module decision | `govoplan-core` | `add-ideas/govoplan-core#196` | +| Datasources for databases, CSV, files, APIs | proposed `govoplan-datasources` | `add-ideas/govoplan-core#197` | +| Dataflow for pipelines, BI, publication | proposed `govoplan-dataflow` | `add-ideas/govoplan-core#198` | +| Templates for letters, emails, forms, reports | `govoplan-templates` | `add-ideas/govoplan-templates#1` | +| Reporting and BI | `govoplan-reporting` | `add-ideas/govoplan-reporting#1` | +| File connectors: Nextcloud, Seafile, SMB, NFS | `govoplan-files` | `add-ideas/govoplan-files#15` | +| Public-sector software integration catalogue | `govoplan-connectors` | `add-ideas/govoplan-connectors#2` | +| Adrema-style address and distribution-list management | `govoplan-addresses` | `add-ideas/govoplan-addresses#1` | +| Consume sources and become a governed source | `govoplan-connectors` plus proposed `govoplan-dataflow` | `add-ideas/govoplan-connectors#3`, `add-ideas/govoplan-core#198` | +| Terminplaner and calendar primitives | `govoplan-calendar` | `add-ideas/govoplan-calendar#1` | +| Terminbuchung appointment booking | `govoplan-appointments` | `add-ideas/govoplan-appointments#1` | +| Collaborative documents | `govoplan-dms` | `add-ideas/govoplan-dms#1` | +| Forms | `govoplan-forms` | `add-ideas/govoplan-forms#1` | +| RSS consume and emit | `govoplan-connectors` | `add-ideas/govoplan-connectors#4` | +| LDAP, Active Directory, OpenDesk identity | `govoplan-idm` | `add-ideas/govoplan-idm#1` | +| OpenDesk stack integration map | `govoplan-connectors` | `add-ideas/govoplan-connectors#5` | +| Open-Xchange mail/groupware | `govoplan-mail` | `add-ideas/govoplan-mail#5` | +| Open-Xchange calendar | `govoplan-calendar` | `add-ideas/govoplan-calendar#2` | ## Proposed Missing Modules -- `govoplan-projects`: project management abstractions and OpenProject integration. -- `govoplan-datasources`: database, CSV, file, API, and external system source definitions. -- `govoplan-dataflow`: pipelines that connect datasources, transform data, and feed BI/reporting outputs. -- `govoplan-reports`: templates, letters, documents, dashboards, exports, scheduled reports, and report rendering. -- `govoplan-file-connectors`: Nextcloud, Seafile, SMB, NFS, WebDAV, S3, and DMS/eAkte storage connectors. -- `govoplan-connectors`: catalogue and runtime for public-sector software integrations, including import/link/replace strategies. -- `govoplan-recipients`: address management, adrema-style recipient lists, email lists, postal-letter recipients, and audience segmentation. -- `govoplan-sources`: consume sources, normalize provenance, publish sources, emit feeds, and track source-to-source workflows. -- `govoplan-calendar`: calendars, scheduling, Terminplaner, Terminbuchung, appointment availability, booking flows, and reminders. -- `govoplan-documents`: collaborative document workflows, document state, review, locking, and file-module boundaries. -- `govoplan-forms`: reusable form definitions, submissions, validation, and workflow handoff. -- `govoplan-opendesk`: integration profile for the OpenDesk stack: Open-Xchange, Nextcloud, OpenProject, LDAP, Active Directory, OIDC/SAML, SCIM, and related shared identity/document/project capabilities. +`govoplan-datasources` should exist only if source catalog ownership becomes broad enough to justify a module separate from connectors and reporting. Candidate responsibilities: -## Integration Questions +- source catalogue for SQL databases, CSV/Excel files, uploaded files, APIs, RSS feeds, and governed file locations +- credentials and connection profiles +- schema discovery and refresh cadence +- provenance, freshness, permission boundaries, and audit events -- Which public-sector systems are common enough to be first-class GovOPlaN connectors? -- For each external system, should GovOPlaN integrate, link, import, synchronize, or replace the workflow? -- Which modules own source consumption versus source publishing? -- Which document collaboration features belong in `govoplan-files`, and which require a separate `govoplan-documents` module? -- Should calendar, appointment booking, and Terminplaner live in one module or split into calendar plus booking modules? -- Should reports/templates be one module initially, or split into document templates, report rendering, and BI dashboards later? +`govoplan-dataflow` should exist only if pipelines and publication become first-class product behavior. Candidate responsibilities: -## Routing Rule +- ingestion, transformation, validation, scheduling, and lineage +- connecting datasources to reports, APIs, RSS, exports, and downstream systems +- the "consume sources, become source" lifecycle +- publication-state and audit integration -Create implementation issues in the owning module repository when the module exists. Create proposal and split-design issues in `govoplan-core` when the module is missing or cross-cutting. +`govoplan-projects` is undecided. The default path should be an OpenProject connector first. A native module is justified only if GovOPlaN must own project semantics beyond cases, tasks, workflow, appointments, documents, and reporting. + +## Boundary Notes + +- `govoplan-connectors` owns protocol and external-system integration strategy. It should not own business semantics once a domain module exists. +- `govoplan-files` owns file storage semantics and file-provider contracts. Remote provider implementations must stay optional. +- `govoplan-dms` owns document lifecycle, collaboration, versions, approvals, locks, retention, and legal hold. +- `govoplan-addresses` owns persons, organizations, postal/email addresses, distribution lists, and recipient import/export. +- `govoplan-calendar` owns events, availability, resources, recurrence, and groupware calendar adapters. +- `govoplan-appointments` owns public/internal appointment-booking workflows. +- `govoplan-idm` owns directory, provisioning, and identity-provider integration; `govoplan-access` consumes resolved principals and permissions. +- `govoplan-reporting` owns report definitions, BI views, scheduled outputs, and export targets. +- `govoplan-templates` owns reusable renderable templates, not data selection or persistence. + +## Release Tooling Note + +`scripts/push-release-tag.sh` currently covers the released full-product set only: + +- `govoplan-access` +- `govoplan-admin` +- `govoplan-tenancy` +- `govoplan-policy` +- `govoplan-audit` +- `govoplan-files` +- `govoplan-mail` +- `govoplan-campaign` +- `govoplan-core` + +It does not currently include the wider module backlog repositories such as addresses, appointments, calendar, connectors, DMS, forms, IDM, reporting, templates, workflow, XOE/V, XRechnung, or proposed datasources/dataflow/projects modules. Extend the release script deliberately before treating those modules as part of the tagged product release train.