potiuk opened a new pull request, #57: URL: https://github.com/apache/airflow-steward/pull/57
## Summary Working draft of the proposal text for establishing Apache `<PROJECT_NAME>` as a Top-Level Project — built on the work that became apache-steward, framed for a Board / committee read. **Sections covered:** - Abstract, Proposal, Proposed Names, Rationale, Initial Goals, Technical scope (modes A/B/C/D) - **Maintainer education** — building agentic projects is a different craft - **Privacy, security, and supply-chain integrity** — load-bearing chapter; top priority - **Affordability and vendor neutrality** — public-good commitment - Initial PMC composition target, Required resources, Source and IP, External dependencies, Cryptography, Particular care, Ask of the Board **Three project-shape claims** the document tries to make explicit: 1. *"Project" includes non-ASF.* ASF integrations live behind clean configuration boundaries; non-ASF adopters are first-class from day one of v1, not later. 2. *Security-issue handling is a load-bearing use case, not a footnote.* Every Mode A/B/C/D capability has to clear the security-flow bar before it ships. 3. *Mentoring is a first-class mode.* The lever the ASF actually needs and the one off-the-shelf agent tooling skips. The References section is intentionally omitted from this initial check-in until the linked RFCs (RFC-AI-0002, RFC-AI-0003) and the ASF Responsible AI Initiative description are public; will land in a follow-up. ## Test plan - [x] Markdown parses cleanly; `pandoc -s MISSION.md -o MISSION.html` renders as expected. - [ ] Initial committee feedback on substance — naming poll, mode boundaries, PMC roster, the affordability/vendor-neutrality commitments. - [ ] Coordination with the Responsible AI Initiative on RFC linkage before the References section lands. -- 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]
