Part of #54.
Summary
Add a ROADMAP.md at the repo root so adopters and contributors can see where the package collection is headed. nodewright has one (ROADMAP.md); this repo does not.
Adaptation required (content is net-new, not a port)
nodewright's roadmap is about the operator's path to v1 (CRD stability, Go agent, OCI packages). None of that content applies here. This issue is to write a packages-specific roadmap, which is a product/maintainer decision rather than a mechanical copy. Suggested structure mirroring nodewright's format:
- Objectives: what "good" looks like for the package collection (quality bar per package, consistent lifecycle, build/release reliability, docs completeness).
- Scope: planned new packages, packages slated for hardening, shared tooling improvements (CI, signing/provenance for package images, test coverage).
- Revision history table.
Note
This one needs maintainer input on direction before it can be written. Flagging it as part of the hygiene sweep because the file is absent; the content is not something to auto-generate. If the team would rather not maintain a roadmap for this repo, close this with that decision recorded.
Acceptance
ROADMAP.md exists with packages-specific objectives and scope, or the issue is closed with an explicit "no roadmap for this repo" decision.
Part of #54.
Summary
Add a
ROADMAP.mdat the repo root so adopters and contributors can see where the package collection is headed. nodewright has one (ROADMAP.md); this repo does not.Adaptation required (content is net-new, not a port)
nodewright's roadmap is about the operator's path to v1 (CRD stability, Go agent, OCI packages). None of that content applies here. This issue is to write a packages-specific roadmap, which is a product/maintainer decision rather than a mechanical copy. Suggested structure mirroring nodewright's format:
Note
This one needs maintainer input on direction before it can be written. Flagging it as part of the hygiene sweep because the file is absent; the content is not something to auto-generate. If the team would rather not maintain a roadmap for this repo, close this with that decision recorded.
Acceptance
ROADMAP.mdexists with packages-specific objectives and scope, or the issue is closed with an explicit "no roadmap for this repo" decision.