[Task] Should govoplan-core be renamed conceptually to govoplan-kernel, while keeping package compatibility for now? #180

Closed
opened 2026-07-06 15:22:02 +02:00 by zemion · 1 comment
Owner

Imported from a backlog-like text file.

  • Source: /mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/split-concept-action-plan.md
  • Line: 429
  • Source kind: product
  • Section: GovOPlaN Split Concept and Action Plan > Key Decisions Needed

Imported item:

Should `govoplan-core` be renamed conceptually to `govoplan-kernel`, while keeping package compatibility for now?
<!-- codex-generic-backlog-fingerprint:e450248a5b748bc5ecbaf4c8 --> Imported from a backlog-like text file. - Source: `/mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/split-concept-action-plan.md` - Line: `429` - Source kind: `product` - Section: `GovOPlaN Split Concept and Action Plan > Key Decisions Needed` Imported item: ```text Should `govoplan-core` be renamed conceptually to `govoplan-kernel`, while keeping package compatibility for now? ```
zemion added this to the Split Concept Action Plan milestone 2026-07-06 15:22:02 +02:00
zemion added the
type
task
priority
p2
source/backlog-import
codex/ready
labels 2026-07-07 23:11:51 +02:00
zemion added the
status
triage
label 2026-07-08 02:26:40 +02:00
Author
Owner

Codex State: done

Summary

  • Decision recorded: keep the package/repository name govoplan-core for compatibility, but treat the architectural target as a smaller platform kernel.

Evidence

  • govoplan-core/docs/MODULE_ARCHITECTURE.md
## Codex State: done ### Summary - Decision recorded: keep the package/repository name `govoplan-core` for compatibility, but treat the architectural target as a smaller platform kernel. ### Evidence - `govoplan-core/docs/MODULE_ARCHITECTURE.md`
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-core#180
No description provided.