You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: OPEN_SOURCE_ADOPTION.md
+15-13Lines changed: 15 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -185,9 +185,9 @@ If I were prioritizing for adoption, I would do this in order:
185
185
| 2 | Trust and safety | P0 | M | Add `--inspect` / dry-run, make data provenance visible, document storage vs model-bound data, and introduce redaction rules. | done |
186
186
| 3 | Proof of value in the output | P0 | M | Tighten the restore brief, emphasize blockers / next actions, and add a compact “changed since last sync” section. | done |
187
187
| 4 | Adapter extensibility | P1 | L | Define adapter contracts, add a registry, move built-ins behind the interface, and document how to add `pi-agent`, `opencode`, or future sources. | done |
188
-
| 5 | Reliability and verifiability | P1 | M | Add fixture-based tests for adapters and snapshots, then wire CI around the core flow. |to-do|
189
-
| 6 | Distribution and package polish | P1 | S | Add `--version`, public install docs, release checklist, and complete package metadata for broader distribution. |to-do|
190
-
| 7 | Contribution surface | P2 | S | Add `CONTRIBUTING.md`, fixture docs, and clearly scoped good-first issues for adapters and tests. |to-do|
188
+
| 5 | Reliability and verifiability | P1 | M | Add fixture-based tests for adapters and snapshots, then wire CI around the core flow. |done|
189
+
| 6 | Distribution and package polish | P1 | S | Add `--version`, public install docs, release checklist, and complete package metadata for broader distribution. |done|
190
+
| 7 | Contribution surface | P2 | S | Add `CONTRIBUTING.md`, fixture docs, and clearly scoped good-first issues for adapters and tests. |done|
191
191
192
192
### Status rules
193
193
@@ -197,17 +197,19 @@ If I were prioritizing for adoption, I would do this in order:
197
197
198
198
## Concrete next work items
199
199
200
-
- add fixture-based tests for the adapters and snapshot rendering
201
-
- add a CI workflow
202
-
- add a minimal contributor guide
203
-
- tighten restore output for “proof of value” (item 3)
200
+
All adoption backlog items are done. Remaining polish:
204
201
205
-
## Notes on current gaps
202
+
- publish to PyPI (`uv build && uv publish`)
203
+
- tag v0.1.0 release on GitHub
204
+
- open “good first issue” tickets for the items listed in `CONTRIBUTING.md`
206
205
207
-
The repo currently has:
206
+
## Notes on current state
208
207
209
-
- no `tests/` directory
210
-
- no CI workflow
211
-
- no visible sample output fixtures (beyond `mind doctor --demo`)
208
+
The repo now has:
212
209
213
-
That means the core product is present, but several adoption and contribution mechanics are still missing.
210
+
-`tests/` with fixture-based adapter and snapshot tests (37 passing)
211
+
-`.github/workflows/ci.yml` running pytest + ruff on Python 3.11 and 3.12
212
+
-`LICENSE` (MIT)
213
+
-`CONTRIBUTING.md` with dev setup, adapter guide, and good-first-issue list
214
+
-`mind --version` reading from package metadata
215
+
- public install instructions in `README.md` (PyPI + from source)
0 commit comments