potiuk opened a new pull request, #485:
URL: https://github.com/apache/airflow-steward/pull/485
## Summary
Adds a "Scope boundaries — what Magpie is, and the non-goals" section to
`MISSION.md`, sitting between Rationale and Initial Goals (with a matching
TOC entry). The mission's capability scope is broad, so this draws an
explicit line on *authority*:
- **Magpie serves any project, ASF or not** — the distinguishing line from
ASF-internal bodies (ComDev, Incubator, Security, Tooling, RAI).
- **Magpie is an ordinary independent PMC that only releases software** — it
sets no Foundation-wide policy and does not tell projects how to govern
themselves (explicit non-goal).
- **Works with, does not absorb** the ASF bodies it overlaps — implements or
*proxies* their skills; teams opt in; other foundations can do the same.
- **Shared data layer, divergent skills** — MCPs/data tools stay centralized;
skills on top diverge by scope/tier/voice, `source`-tagged and proxied.
- **Duplication embraced for decoupling**, with eventual consistency required
only on the safety baseline.
- **Mentoring is tooling, not a role claim** — Magpie ships mentoring skills;
the community-development mentoring function stays ComDev's (and, for
podlings, the Incubator's) for ASF projects.
## Type of change
- [X] Documentation (`docs/`, `README.md`, `CONTRIBUTING.md`)
## Test plan
- [X] `prek run --all-files` passes (pre-commit hooks ran clean on commit)
---
Generated-by: Claude Code (Opus 4.8)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
