Skip to content

ROADMAP.md

Latest commit

 

History

History
83 lines (53 loc) · 4.49 KB

ROADMAP.md

File metadata and controls

83 lines (53 loc) · 4.49 KB

Project Roadmap

Table of Contents

Vision

  • Keep socket as the honest superproject layer for Gale's public Codex plugin and skills ecosystem, with subtree imports, root marketplace wiring, and cross-repo maintainer guidance kept consistent.

Product Principles

  • Keep the superproject focused on subtree coordination, root marketplace wiring, and cross-repo maintainer guidance.
  • Keep child-repository ownership boundaries explicit instead of flattening repo-local behavior into socket.
  • Keep public imported plugin surfaces and root marketplace wiring aligned in the same pass.

Milestone Progress

  • Milestone 2: subtree workflow hardening - Planned
  • Milestone 3: release and sync discipline - In Progress

Milestone 2: subtree workflow hardening

Status

In Progress

Scope

  • Tighten the documented subtree add, pull, and push workflows without changing the child-repo ownership model.

Tickets

  • Review subtree workflow docs against the current import and publish path.

Exit Criteria

  • Root maintainer workflow docs describe the actual subtree sync path without stale or duplicate guidance.

Milestone 3: release and sync discipline

Status

Planned

Scope

  • Keep root release and synchronization guidance explicit when superproject-level changes ship.

Tickets

  • Document the expected root release and sync rhythm once the current subtree migration experiment stabilizes.
  • Keep the root docs aligned with the current child packaging model during coordinated release-prep passes.
  • Make coordinated semantic-version bumps across socket and the maintained child manifests explicit instead of relying on ad hoc release notes.

Exit Criteria

  • Superproject release guidance is explicit enough that root changes can be shipped without improvising process each time.
  • Root docs still describe the live packaging and versioning model after a coordinated release-prep pass.

Backlog Candidates

  • Add a documented audit pass for detecting stale child packaging paths in the root marketplace.
  • Add a superproject-level checklist for removing public child repos that should no longer be imported.

History

  • Added the placeholder plugins/spotify child repository, wired it into the root marketplace, and kept the superproject docs honest about that new monorepo-owned plugin surface.
  • Converted the former standalone cardhop-mcp checkout into the monorepo-owned plugins/cardhop-app child, added first-pass Codex plugin metadata plus a bundled MCP config, and recorded the new child as a normal socket marketplace entry.
  • Retired the remaining things-app subtree-era wording from the root maintainer docs, removed the now-redundant local things-app and things-app-mcp sibling checkouts after verification, and prepared the v0.11.1 plus things-app v0.1.3 patch bump.
  • Synced the SpeakSwiftlyServer subtree through the newer v4.2.x plugin and embedded live-speech updates, confirmed the root marketplace path still stayed valid, and kept the superproject release trail explicit with the v0.11.0 bump.
  • Added a root version-alignment script, switched python-skills to the monorepo-owned workflow, and documented the shared-version policy for the maintained manifest surfaces.
  • Completed Milestone 1, superproject docs and marketplace alignment, by bringing the root README, AGENTS guidance, roadmap shape, and marketplace-path explanation back into alignment with the live mixed-monorepo model.
  • Added the first root ROADMAP.md and established the checklist-style planning format for the superproject.
  • Added a root marketplace-validation script and GitHub Actions workflow so socket now checks packaged plugin paths and manifest alignment instead of leaving that audit entirely manual.
  • Added root CONTRIBUTING.md, ACCESSIBILITY.md, LICENSE, and NOTICE so the superproject's contributor, accessibility, and legal surfaces are explicit at the repository root.
  • Collapsed the older subtree migration and plugin-alignment planning docs into this roadmap history plus the still-live root maintainer references once those plans had become historical rather than active operating guidance.