This was extracted (@ 2026-09-18 21:10) from a list of minutes
which have been approved by the Board.
Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.
ASF Members may have access to a
private draft
WARNING: these pages may omit some original contents of the minutes.
Report was filed, but display is awaiting the approval of the Board minutes.
Report was filed, but display is awaiting the approval of the Board minutes.
## Description: Apache Magpie is responsible for the creation and maintenance of software related to agent-assisted repository maintainership and development — including issue and pull-request triage, contributor mentoring, agent-drafted remediation, developer-side development-cycle skills, and narrowly-scoped fix-and-merge automation. Magpie is deliberately governance-agnostic: it is built to be adopted by ASF projects and by non-ASF open-source projects alike, with no ASF-only assumption baked into the install path. ## Project Status: - First committer votes succeded — three candidates, our first since establishment. These are committer votes only; whether committers should automatically join the PMC remains an open question the PMC is discussing separately. We are proceeding with inviting and formalising it. - PMC/Committers: 22 members. Chair: Jarek Potiuk. No additions or removals in the period. - Apache Magpie 0.1.0 — 2026-07-18. Our first release. - Cut via a hybrid path: the Apache Trusted Releases (ATR) platform with the traditional manual process as fallback. We used the fallback when ATR hit blocking issues, and fed that experience back to the ASF Tooling team. - Two release candidates were needed; rc1 was withdrawn after review feedback. We consider that the process working rather than a problem. - The release was itself driven by Magpie's own release skills — dogfooding that surfaced real defects we have since fixed. No new issues. As noted last month, the PMC is exploring relationships with other open-source organisations. These remain exploratory discussions only; nothing formal will be done without first engaging VP Marketing & Publicity. The initial discussions had shown that while there is interest - the installation approach for Python Software Foundation use and other non-ASF projects might be a blocker. Eclipse is more interested in having Enclave embedded as part of the sandboxing. Both approaches are in the discussion phase. Thanks for clarifying our question from last month. ## Membership Data: Apache Magpie was founded 2026-06-17 (2 months ago) There are currently 22 committers and 22 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members (project became TLP recently). - Three new commmitters are already accepted, formalising the process was a little impaired due to PMC chair attending Community Over Code Asia. ## Project Activity: Ongoing, medium activity. The project has shipped its first Apache release and is now moving from bootstrapping into normal operation. Discussion at Community Over Code Asia - where three PMC members (Jarek, Craig and Justin) were speaking had shown that Magpie addresses the very problems many of the PMCs in Asia are also struggling with. Magpie was mentioned multiple times at Keynotes and other talks (alongside RAI initiative as well). The discussions (also earlier ones) allowed to identify two main bottlenecks for adoption: * Installation process * Too many interruptions due to security / permissions Luckily those are common industry problems and industry is converging on solutions: Marketplace and Plugin standards have just been released by Open AI and Anthropic, and permission models for CLI is changing to "auto-approve by default". We are going to leverage both in the next version - while we are going to build addional security layer, which will maintain current security level while avoiding too frequent interruptions. - 162 pull requests merged in the period, across roughly 37 contributors. - Governance tightened. Approval-before-merge is now enforced by branch protection; the project no longer self-merges without review. This was a deliberate slowdown following the release. - 0.2.0 focus is adoption friction. - Trusted external skill sources (RFC-AI-0006) landed, allowing skills to be pulled from trusted external repositories — the mechanism the PSF conversation depends on. - Vendor neutrality remains automatically measured and published at 100% across capability contracts, skills, and agent harnesses: https://magpie.apache.org/#vendor-neutrality - Framework now at 70 skills and 45 tools. - A read-only repo-health audit family shipped: Actions workflow security, dependency vulnerabilities, licence and NOTICE compliance, and flaky-test patterns. These skills observe and report only; they make no changes, consistent with the project's human-in-the-loop discipline. ## Community Health: Healthy and broadening, with some caveats. Contribution is still concentrated: Jarek and Justin account for a large share of commits. But the tail has grown — several contributors now show sustained, substantive activity, and the three committer votes now running are the first step in converting that into shared responsibility. Enforcing review-before-merge was the other half of that deliberately, since it forces work through more than one pair of hands. Interest continues from outside the ASF, including a contributor with professional AI-security and privacy background who approached the list directly. The Chair was presenting a Magpie talk and the security keynote at Community Over Code Asia, We are also discussing an ASF blog post intended to carry perspectives from adopters rather than only from the PMC. Further events that are coming where we can get further feedback are Airflow Summit and Community Over Code Glasgow. Ongoing community discussion: ASF Slack requires guest invites for non-ASF participants, which conflicts with our goal of being open to adopters outside the foundation. The PMC is deciding between Matrix and Discord for an open channel. Onboarding investment has improved. An 11-lesson AI tutor curriculum now ships in the repository, giving new contributors and adopting maintainers a structured path into the framework. Also for the upcoming release (0.2.0) we are reviewing all the SKILLs, docs onboarding docs for consistency. While Agentic driven development is great to move fast, it also breaks some consistency, miscount things and hallucinates sometimes, we are not only fixing the inconsistencies but adding harnesses to avoid those in the future. A sustained good first issue programme has raised around 60 curated newcomer issues, with 45 closed and roughly 25 distinct external contributors, with several now repeat contributors.
WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to creation and maintenance of software related to agent-assisted repository maintainership and development, including issue and pull- request triage, contributor mentoring, agent-drafted remediation, developer-side development-cycle skills, and narrowly-scoped fix-and- merge automation. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Magpie Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Magpie Project be and hereby is responsible for the creation and maintenance of software related to creation and maintenance of software related to agent-assisted repository maintainership and development, including issue and pull- request triage, contributor mentoring, agent-drafted remediation, developer-side development-cycle skills, and narrowly-scoped fix-and- merge automation; and be it further RESOLVED, that the office of "Vice President, Apache Magpie" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Magpie Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Magpie Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Magpie Project: * Rich Bowen <rbowen@apache.org> * Zili Chen <tison@apache.org> * Amogh Desai <amoghdesai@apache.org> * Mike Drob <mdrob@apache.org> * James Fredley <jamesfredley@apache.org> * Elad Kalif <eladkal@apache.org> * Piotr Karwasz <pkarwasz@apache.org> * Paul King <paulk@apache.org> * Calvin Kirs <kirs@apache.org> * Pavan Kumar <gopidesu@apache.org> * Rémy Maucherat <remm@apache.org> * Justin Mclean <jmclean@apache.org> * Ismaël Mejía <iemejia@apache.org> * Andrew Musselman <akm@apache.org> * Jean-Baptiste Onofré <jbonofre@apache.org> * Jarek Potiuk <potiuk@apache.org> * Evan Rusackas <rusackas@apache.org> * Craig L Russell <clr@apache.org> * Russell Spitzer <russellspitzer@apache.org> * Coty Sutherland <csutherl@apache.org> * Matthew Topol <zeroshade@apache.org> * Richard Zowalla <rzo1@apache.org> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jarek Potiuk be appointed to the office of Vice President, Apache Magpie, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7C, Establish the Apache Magpie Project, was approved by Unanimous Vote of the directors present.
WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to creation and maintenance of software related to agent-assisted repository maintainership and development, including issue and pull- request triage, contributor mentoring, agent-drafted remediation, developer-side development-cycle skills, and narrowly-scoped fix-and- merge automation. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Magpie Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Magpie be and hereby is responsible for the creation and maintenance of software related to creation and maintenance of software related to agent-assisted repository maintainership and development, including issue and pull- request triage, contributor mentoring, agent-drafted remediation, developer-side development-cycle skills, and narrowly-scoped fix-and- merge automation; and be it further RESOLVED, that the office of "Vice President, Apache Magpie" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Magpie Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Magpie Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Magpie Project: * Andrew Musselman <akm@apache.org> * Amogh Desai <amoghdesai@apache.org> * Craig L Russell <clr@apache.org> * Elad Kalif <eladkal@apache.org> * Pavan Kumar <gopidesu@apache.org> * Ismaël Mejía <iemejia@apache.org> * James Fredley <jamesfredley@apache.org> * Jean-Baptiste Onofré <jbonofre@apache.org> * Justin Mclean <jmclean@apache.org> * Calvin Kirs <kirs@apache.org> * Mike Drob <mdrob@apache.org> * Paul King <paulk@apache.org> * Piotr Karwasz <pkarwasz@apache.org> * Jarek Potiuk <potiuk@apache.org> * Rich Bowen <rbowen@apache.org> * Evan Rusackas <rusackas@apache.org> * Russell Spitzer <russellspitzer@apache.org> * Zili Chen <tison@apache.org> * Matthew Topol <zeroshade@apache.org> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jarek Potiuk be appointed to the office of Vice President, Apache Magpie, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Establish the Apache Magpie Project, was tabled.
