Hi, Do you have example from JMeter gitHub?
Le lun. 6 juil. 2026 à 17:01, Milamber <[email protected]> a écrit : > Hi all, > > I'd like to gauge the PMC's and committers' appetite for adopting Apache > Magpie in the JMeter repository. > > What it is > ---------- > Apache Magpie is an ASF framework of "agent skills" -- structured, > auditable workflows an AI coding agent (e.g. Claude Code) can run to assist > maintainer and PMC tasks. It's a shared, versioned playbook for the project > rather than each of us improvising prompts. > > What it offers (each maintainer picks what they use) > ---------------------------------------------------- > - PR queue: triage, code review with inline comments, quick-merge > candidates, stats dashboards > - Issues: triage, deduplication, stale sweeps, reproducers, backlog stats > - Security: import/triage of reports, CVE-allocation helpers, tracker sync > -- aligned with the ASF security process > - Releases: RC cut, [VOTE] drafting and tally, promotion, [ANNOUNCE] drafts > - Contributors: nomination briefs, good-first-issue sweeps, mentoring > drafts > > Why it's low-risk > ----------------- > - Human-in-the-loop: nothing runs automatically. Each skill only > *proposes*; a human confirms before any comment, merge, or commit. No bots > posting on their own, no CI automation. > - Small repo footprint: the framework is not vendored -- a gitignored > snapshot is fetched on demand, and only a small "setup" skill plus a little > config is committed. Full removal is a single command. > - Local and credential-scoped: it runs inside each maintainer's own agent, > under their own credentials. No shared service; no project data leaves > where the maintainer controls it. > > I've prototyped the adoption on a branch: it works cleanly with our GitHub > Issues, the dev@/private@ lists (via the ASF PonyMail archive), and the > ASF > CVE tooling. > > Before I open a PR, I wanted to check with you: are the PMC and committers > OK with integrating Magpie (directly the Method 3 — git branch - main) ? > Any concerns about the committed footprint, security, or governance are > very welcome. I'll treat the usual lazy-consensus window (72h) as > agreement, but I'd genuinely prefer to hear your thoughts. > > For me, Magpie can help to have more activities on JMeter, and help to > prepare the next release. > > Reference: https://magpie.apache.org/ > > Thanks, > Milamber >
