Skip to content

Cleanup: decide archive vs keep for spool-rack repo #116

Description

@pewpewpotato

Problem

spool-rack is product-sunset but the repo artifact may still look live (README/About/CI).

Who it’s for

Anyone discovering spool-rack on GitHub; maintainers avoiding false “ship this” signals.

Acceptance criteria

  • Explicit decision: archive vs keep-for-history only
  • If archive: GitHub archive + README banner pointing at Spool git-SoT / migrate-once
  • About/CI don’t imply an active Rack product path
  • Spool docs don’t link to Rack as a happy-path dependency

Priority

Second of the post-pivot cleanup slice (after skills audit).

Owner

Werner (decision) + Spool Technical Lead (apply)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions