Skip to content

Simplify readme#901

Closed
meonkeys wants to merge 5 commits into
apache:mainfrom
meonkeys:simplify-readme
Closed

Simplify readme#901
meonkeys wants to merge 5 commits into
apache:mainfrom
meonkeys:simplify-readme

Conversation

@meonkeys

@meonkeys meonkeys commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Summary

  • greatly simplified readme

Fix #899.

This PR builds on #898. Please merge that one first, or if that one won't be merged just LMK and I'll rebase on main. Because of this, the "Files changed" tab won't make sense. You can review only the changes for this PR at meonkeys@ba9bce0

Type of change

  • Skill change (.claude/skills/<name>/) — eval fixtures updated below
  • Tool / bridge contract (tools/<system>/*.md)
  • Python package (tools/*/ with pyproject.toml)
  • Groovy reference impl
  • Cross-cutting (RFC, AGENTS.md, sandbox, privacy-LLM)
  • Documentation (docs/, README.md, CONTRIBUTING.md)
  • Project template (projects/_template/)
  • CI / dev loop (prek, workflows, validators)
  • Other:

After making changes I ran doctoc. I used doctoc v2.5.0.

Test plan

not applicable

RFC-AI-0004 compliance

not applicable, AFAICT

Linked issues

None. This is a drive-by PR but I'll stick around to absorb feedback, discuss, improve, etc.

Notes for reviewers (optional)

I joined the #magpie Slack channel in case you want to ping me in there. My handle is meonkeys in there as well.

meonkeys added 5 commits July 16, 2026 10:37
Just a suggestion. I started this patch to fix the duplication of the
words "creation and maintenance of software related to" and then ended
up rewriting the whole thing, mostly based on the (IMHO better) wording
I found at https://magpie.apache.org .
This is a readme, not an architecture showcase. I pared it down to more
of a "quick start" type of doc. Lots of the text is duplicated in gory
detail elsewhere in the docs / skills.

"Public marketplace skill" didn't mean anything special to me so I went
with just "in testing" (when I said "Testers welcome!").

I didn't find the unfamiliar "adoption" terminology helpful either.
Culled, and replaced with the much more standard (IMHO) "install". If we
really want to use new/nonstandard words, we should include a glossary.

After making changes I ran doctoc. I used doctoc v2.5.0.

fix apache#899
@potiuk

potiuk commented Jul 19, 2026

Copy link
Copy Markdown
Member

please fix the prek/conflicts

potiuk added a commit to potiuk/magpie that referenced this pull request Jul 19, 2026
…l (adopt alias)

Folds the top-level README simplification from apache#901 (by @meonkeys) into the
0.2.0 marketplace work, and shifts the primary term to 'install' now that
marketplace installation exists:

- Keeps Adam's simplified Install / Usage / Update / Skill-families structure.
- Install section covers both paths: agent marketplace (easiest, nothing
  committed) and the committed snapshot via /magpie-setup.
- 'install' is the primary verb/command; '/magpie-setup adopt' stays an alias;
  'Adopt a Magpie' remains the landing-page slogan; 'adopter'/'adopter repo'
  kept as the ecosystem noun.
- Repoints inbound doc links from the removed README#adopting-the-framework
  anchor to README#install and updates their labels.

Supersedes the standalone apache#901 (its Fix apache#899 goal already merged via apache#905).
Credit to @meonkeys for the simplification.
@potiuk

potiuk commented Jul 19, 2026

Copy link
Copy Markdown
Member

Thanks @meonkeys — this simplification is a real improvement, and I've folded it into #907 (the 0.2.0 marketplace PR), where the README also gains the marketplace install path and leads with "install" (with "adopt" kept as an alias and "Adopt a Magpie" as the slogan). Your Install/Usage/Update structure is preserved.

Since #899 (this PR's Fix target) is already closed via #905, and #907 now carries your README work reconciled with the marketplace changes, I'm closing this as superseded by #907. Credit for the simplification is in the fold commit — thank you!

@potiuk potiuk closed this Jul 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

confusing wording in top-level README

2 participants