docs: community reach ideas + Pharo 12/13/14 compatibility plan#13
Merged
docs: community reach ideas + Pharo 12/13/14 compatibility plan#13
Conversation
Records the repositioning pitch (Postern as Pharo release engineering tool for 12/13/14 work), target audience map, new-endpoint ideas (/info, /smoke, version-aware /help), the postern-matrix multi-image helper, distribution channels (Pharo catalog, pharo-ci-matrix companion repo, ESUG talk), and three principles to keep the repositioning credible (tiny + stable, zero Anthropic surface, path to Pharo core adoption). None of these are commitments. The file exists so the conversation has a durable artifact to return to. Multi-version Postern support itself is planned separately.
Records the configuration management decision for supporting multiple Pharo versions: single main branch, shared Postern-Core, per-version Postern-Compat-PharoN shim packages selected via Metacello 'for:' conditionals. Rejects long-lived version branches, parallel packages, and runtime Smalltalk version checks with rationale for each. Includes six-PR execution plan (compat seam on Pharo 12 first, then baseline rewrite, then Pharo 13 support, then CI matrix, then Pharo 14, then docs/release), layout diagram, BaselineOfPostern structure, compat API example, and the four signals that the structure is breaking down.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 544d765. Configure here.
There was a problem hiding this comment.
Pull request overview
Adds two planning documents capturing Postern’s positioning/community outreach ideas and a proposed approach for maintaining Pharo 12/13/14 compatibility without long-lived branches or duplicated core packages.
Changes:
- Add
docs/ideas.mdwith potential roadmap/distribution ideas for repositioning Postern as a Pharo release-engineering tool. - Add
docs/pharo-compat.mddescribing a Metacellofor:+ per-version compat-shim strategy and an execution plan for Pharo 13/14 support. - (Incidental) Adds
.beads/*.jsonltracker artifacts.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| docs/pharo-compat.md | Compatibility strategy + baseline/CI plan for Pharo 12/13/14. |
| docs/ideas.md | Community reach + endpoint/orchestration ideas for broader Pharo use. |
| .beads/issues.jsonl | Tracker state JSONL added incidentally (non-doc scope). |
| .beads/interactions.jsonl | Empty tracker file added incidentally (non-doc scope). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Bugbot + Copilot (8 threads, all addressed): - Dropped .beads/interactions.jsonl and .beads/issues.jsonl from tracking. These were internal tracker artifacts accidentally swept in by git add. Three reviewers flagged them independently. - pharo-compat.md: fixed repo layout diagram — BaselineOfPostern lives at src/BaselineOfPostern/, not top-level. - pharo-compat.md: compat packages now require Postern-IcebergExtensions (not just Postern-Core) so extension methods load after the classes they extend. - pharo-compat.md: standardized compat-package size threshold to 20 classes (was inconsistent: 15 in principles, 20 in signals). - ideas.md: corrected 'append-only eval log' claim — Postern uses a bounded ring buffer (PosternRequestLogger); rephrased to describe current behavior and mark append-only as future idea.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two new docs capturing recent planning conversations around Postern's future.
What changed
docs/ideas.mdCaptures a forward-looking pitch for repositioning Postern as a Pharo release engineering tool rather than just "the Claude SDK's image driver." Includes:
/info(environment fingerprint),/smoke(scripted test battery), Pharo-version-aware/helppostern-matrixCLI sketch for multi-image orchestrationpharo-ci-matrixrepo, ESUG talkNone of these are commitments — the file exists so the conversation has a durable artifact to return to.
docs/pharo-compat.mdThe configuration management plan for extending stable Postern to Pharo 13 and 14. Key decisions:
mainbranch, sharedPostern-Core, per-versionPostern-Compat-PharoNshim packages selected via Metacellofor: #'pharoN.x'conditionalsSmalltalk versionchecks with rationale for eachScope note
The first commit (
06f6351) also incidentally carries.beads/interactions.jsonland.beads/issues.jsonl. Those were sitting untracked in the worktree (not gitignored), sogit add docs/ideas.mdswept them in. The content is Punt Labs tracker state that predates this PR — legitimate content, off-topic for a docs-only PR. Merge as-is or ask me to amend, your call.Test plan
Note
Low Risk
Low functional risk since changes are documentation-only, but it introduces
.beads/issues.jsonltracker content that may be unintended/sensitive to ship publicly.Overview
Adds two new planning docs:
docs/ideas.md(repositioning/roadmap ideas for broader Pharo community reach) anddocs/pharo-compat.md(a proposed approach and rollout plan for supporting Pharo 12/13/14 via compat shim packages and Metacellofor:conditionals).Also adds
.beads/issues.jsonl, a set of internal tracking issues unrelated to the docs content, which expands the repo surface area and may not be intended for release.Reviewed by Cursor Bugbot for commit 3ca399e. Bugbot is set up for automated code reviews on this repo. Configure here.