docs: reflect Apache Magpie's established-TLP status#817
Merged
Conversation
Apache Magpie was established as an ASF Top-Level Project by Board resolution on 17 June 2026. Drop the pre-TLP / Airflow-umbrella / incubator-podling framing across the repo: - .asf.yaml: refresh the github description to the current mode shipping status (Triage, Mentoring, Drafting, Pairing shipping; Agentic Autonomous on the roadmap), and update the branch- protection and notifications comments from "under the Airflow PMC umbrella / will move to its own TLP" to the established-TLP reality. - README.md: MISSION.md is the founding mission of the established TLP, originally filed as its establishment proposal. - MISSION.md / docs/board-resolution-draft.md: add an established-TLP status banner (resolution adopted 17 June 2026); keep the proposal and resolution text as a historical record. - docs/rfcs/RFC-AI-0002.md: apache/magpie is a Top-Level Project, not an incubator-podling. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Member
Author
|
Split out the branch-protection rule change into #818. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Apache Magpie was established as an ASF Top-Level Project by Board resolution on 17 June 2026. This PR drops the pre-TLP / Airflow-umbrella / incubator-podling framing across the repo so the docs and repo config describe the current reality.
Changes
.asf.yaml— refresh thegithub.descriptionto the current mode shipping status (Triage, Mentoring, Drafting, Pairing shipping; Agentic Autonomous on the roadmap), and update the branch-protection and notifications comments from "under the Airflow PMC umbrella / will move to its own TLP" to the established-TLP reality.README.md—MISSION.mdis now framed as the founding mission of the established TLP, originally filed as its establishment proposal.MISSION.md/docs/board-resolution-draft.md— add an established-TLP status banner (resolution adopted 17 June 2026); the proposal and resolution text are kept as a historical record.docs/rfcs/RFC-AI-0002.md—apache/magpieis a Top-Level Project, not an incubator-podling.Notes
.asf.yamlchange — the branch-protection rule (requiring an approving review) is deliberately split into a separate PR (infra/require-review-on-main). The two touch adjacent.asf.yamlcomment lines, so whichever merges second will need a trivial rebase.pre-release/ adoption-by-invitation wording in the README is intentionally left as-is: that describes software release status, which is orthogonal to TLP governance status.🤖 Generated with Claude Code