Packages for v1: define scope or defer (currently spec-less) #634

New issue

Open

opened 2026-09-28 18:55:24 +00:00 by crueber · 0 comments

crueber commented

2026-09-28 18:55:24 +00:00

Owner

Source: OSS-8 close-out audit (Paperclip).

README v1 list shows '- [ ] packages' with no link, and there is nothing behind it:

No spec doc (docs/features/ covers 01-13: identity, issues, PRs, review, checks, notify, releases, UI/SDK, rollout, import, mirror, runner, push-mirror - no packages).
No internal/ package, no routes, no web pages, no SDK module (verified by search).
Note: docs/go/16_packaging.md is container/operator packaging (Dockerfile, compose), NOT a package registry - unrelated.
Partial overlap already shipped: release assets (internal/releases two-step upload + static byte serving) cover downloadable build artifacts.

Before any code, v1 needs a scope decision:

(a) Defer packages past v1 (keep README unchecked, move to v1.1/backlog with a named scope), or
(b) Scope an MVP (which ecosystems? generic files? OCI/container? npm/cargo? tightest fit with the bucket-is-the-database law wins).

Done = this issue records the decision; if (b), a docs/features/NN spec doc is written first (object family, routes, UI/SDK shapes) before implementation. Recommend (a): pulls/releases close out v1, packages is the largest remaining unknown after actions (#288).

Source: OSS-8 close-out audit (Paperclip). README v1 list shows '- [ ] packages' with no link, and there is nothing behind it: - No spec doc (docs/features/ covers 01-13: identity, issues, PRs, review, checks, notify, releases, UI/SDK, rollout, import, mirror, runner, push-mirror - no packages). - No internal/ package, no routes, no web pages, no SDK module (verified by search). - Note: docs/go/16_packaging.md is container/operator packaging (Dockerfile, compose), NOT a package registry - unrelated. - Partial overlap already shipped: release assets (internal/releases two-step upload + static byte serving) cover downloadable build artifacts. Before any code, v1 needs a scope decision: (a) Defer packages past v1 (keep README unchecked, move to v1.1/backlog with a named scope), or (b) Scope an MVP (which ecosystems? generic files? OCI/container? npm/cargo? tightest fit with the bucket-is-the-database law wins). Done = this issue records the decision; if (b), a docs/features/NN spec doc is written first (object family, routes, UI/SDK shapes) before implementation. Recommend (a): pulls/releases close out v1, packages is the largest remaining unknown after actions (#288).

crueber added this to the v1 milestone

2026-09-28 18:55:24 +00:00

crueber added the

packages

label

2026-09-28 18:55:24 +00:00