add-ideas/govoplan-core
1
0
Fork 0
Code Issues 45 Pull Requests Actions Packages Projects Releases Wiki Activity
Files
150b720f120ec73d0fe6070e9f38252ff1b58e2e
govoplan-core/docs/GOVOPLAN_MODULE_ROADMAP.md
Albrecht Degering 150b720f12 Release v0.1.6
2026-07-07 16:00:38 +02:00

5.5 KiB
Raw Blame History

GovOPlaN Module And Integration Roadmap

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.

Current Routing

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
Terminfindung and meeting scheduling polls govoplan-scheduling local scaffold; remote creation tracked by add-ideas/govoplan-core#199
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-datasources should exist only if source catalog ownership becomes broad enough to justify a module separate from connectors and reporting. Candidate responsibilities:

  • 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

govoplan-dataflow should exist only if pipelines and publication become first-class product behavior. Candidate responsibilities:

  • 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

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-scheduling owns meeting scheduling polls, participant availability collection, candidate-slot ranking, and decision handoff.
  • 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 covers the released full-product package set:

  • govoplan-access
  • govoplan-admin
  • govoplan-tenancy
  • govoplan-policy
  • govoplan-audit
  • govoplan-files
  • govoplan-mail
  • govoplan-campaign
  • govoplan-calendar
  • govoplan-core

It also includes existing roadmap/scaffold module repositories such as addresses, appointments, connectors, DMS, forms, IDM, reporting, scheduling, templates, workflow, XOE/V, and XRechnung as tag-only repositories. Tag-only repositories are committed, tagged, and pushed with the same release tag, but they are not added to requirements-release.txt or webui/package.release.json until they contain installable package metadata.

Proposed modules without repositories, such as govoplan-datasources, govoplan-dataflow, and possibly govoplan-projects, cannot be included until their repositories are created.