potiuk opened a new pull request, #143: URL: https://github.com/apache/airflow-steward/pull/143
## Summary The 8–12 May 2026 founding-PMC bikeshed has converged on four names in priority order. A [LAZY CONSENSUS] call is in flight on the founding-PMC mailing thread (deadline **Friday 15 May 2026, 12:00 UTC**); a parallel formal trademark suitability check is in flight with \`[email protected]\`. The candidate list and timeline live in two places by intent: - \`README.md\` — adopter-facing "Heads-up" preamble at the top - \`MISSION.md\` — Board-resolution-facing *Proposed Names* section Both are now updated. ## The four names 1. **Apache Magpie** — primary (10 endorsements in the thread; cleanest mission-fit metaphor; small AI-paper overlap but no commercial mark) 2. **Apache Beacon** — backup 1 (cleanest trademark surface of the four per Justin's MCP run) 3. **Apache Guild** — backup 2 (3 endorsements; The Guild / Guild Education / Guild.xyz trademark headwind in the developer-tooling space) 4. **Apache Lichen** — backup 3 (late-surfaced 13 May; the strongest mission-metaphor of the four — symbiosis maps to RFC-AI-0004 directly — but pronunciation ambiguity and dermatology-SERP collision keep it as fallback) The first of these to clear \`trademarks@\`'s formal review becomes the final name the 20 May Board resolution carries. ## What this PR does **not** touch - The \`<PROJECT_NAME>\` placeholder convention throughout \`MISSION.md\` body, \`docs/modes.md\`, etc. — those stay as placeholders until \`trademarks@\` clears one name. - The repo slug \`apache/airflow-steward\` — rename only lands on the GitHub side after Board adoption. ## Test plan - [x] \`prek run --files README.md MISSION.md\` clean - [ ] Visual review of the README preamble — does the four-line shortlist read as cleanly in the rendered Markdown as it does in source? - [ ] Visual review of the MISSION *Proposed Names* section 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
