docs: surface upcoming repo rename + list candidate names for the working-group poll#37
Merged
Merged
Conversation
…EADME + AGENTS.md The repository is in the process of being renamed from `apache/airflow-steward` to `apache/steward` to reflect its project-agnostic identity. Surface the rename status prominently so adopters and casual visitors aren't confused by the legacy slug in clone URLs / submodule paths. Top-level README: - Title changes from `apache-steward` to `Apache Steward (to be renamed)` so the rename status shows up in every link / GitHub preview / search-result snippet. - Adds a `> Heads-up — rename in flight.` blockquote up front explaining the situation: rename target (`apache/steward`), why (project-agnostic, not Airflow-specific), what stays the same until the rename lands (clone URLs, submodule paths, CI integration — all path examples in the docs use the legacy slug verbatim), and what existing adopters need to do once it lands (a single `git remote set-url`). AGENTS.md: - Same `currently … to be renamed` phrasing in the `Repository purpose` section, with a pointer back to the README's heads-up block. doctoc TOC regenerated. Generated-by: Claude Code (Claude Opus 4.7)
Update the README + AGENTS.md heads-up to reflect that: - The new name is **not** `apache/steward` — it will be a different, yet-to-be-chosen name. The framework is project- agnostic (stewards multiple ASF project workflows), and the working group steering it will pick the new name that reflects that. - The final name will be chosen by **discussion followed by a poll** among the working-group members. - The candidate list is open for additions during the **week of 4–9 May 2026**, after which the poll opens. Current candidate names listed in the README: - Apache Mentor - Apache Reeve - Apache Guild - Apache Minerva - Apache Magpie - Apache Beacon - Apache Compass - Apache Lexicon - Apache Polyglot AGENTS.md updated correspondingly to remove the `apache/steward` target reference and point at the README heads-up for the candidate list and timeline. Generated-by: Claude Code (Claude Opus 4.7)
6 tasks
potiuk
added a commit
that referenced
this pull request
May 3, 2026
…sm (#38) Replace the submodule-based adoption design with snapshot + agentic overrides. One skill (setup-steward) lives committed in the adopter repo; everything else flows from it. The setup-steward skill (multi-file) .claude/skills/setup-steward/ ├── SKILL.md entry point + sub-action dispatch + golden rules ├── adopt.md first-time install — detect convention, │ download snapshot, gitignore, symlinks, │ .apache-steward-overrides/ scaffold, │ post-checkout hook, project-doc note ├── upgrade.md refresh snapshot + reconcile overrides ├── verify.md read-only health check ├── conventions.md skills-dir convention auto-detection │ (flat vs double-symlinked) └── overrides.md interactive override scaffolder Sub-actions /setup-steward — first-time adoption (default) /setup-steward upgrade — refresh the gitignored snapshot /setup-steward verify — health check /setup-steward override <skill> — open / scaffold an override Replaces (folded into setup-steward as sub-actions) - setup-steward-upgrade → /setup-steward upgrade (snapshot mechanics, not git pull) - setup-steward-verify → /setup-steward verify Adoption mechanism - The framework lives at <adopter>/.apache-steward/ as a gitignored --depth=1 git checkout (or, once official ASF releases ship per https://www.apache.org/legal/release-policy.html, a signed tarball from the canonical ASF dist mirrors per https://infra.apache.org/release-distribution.html). - Framework skills are accessed via gitignored symlinks in the adopter's existing skill directory, matching whichever convention the adopter uses (flat or double-symlinked). - Adopter modifications to framework workflows live as agent-readable markdown under .apache-steward-overrides/, committed in the adopter repo. The framework's skills consult those files at run-time and apply the overrides before executing default behaviour. Hard rule: agents NEVER modify the snapshot — local mods go to overrides; framework changes go via PR to apache/airflow-steward. Agentic-override design contract New top-level docs/setup/agentic-overrides.md captures: - where override files live and what they may contain - how a framework skill consults overrides at run-time - hard rules on what the framework agent will never do - reconciliation flow on framework upgrade - upstreaming an override (PR against the framework) - why agentic, not declarative (variance trade-off accepted in exchange for restructure-survival + free-form expression) README rewrite Top-level README is reshaped around the new adoption flow: - "How adoption works" (snapshot + overrides in 3 bullets) - "Adopting the framework" (`tell your agent: 'adopt apache/airflow-steward in my repo'` + the 3-step agentic flow that follows) - The rename heads-up + candidate-name list (kept from #37) - Skill-family overview (setup / security / pr-management) - Maintenance commands Generated-by: Claude Code (Claude Opus 4.7)
andreahlert
added
the
mode:platform
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
2 participants
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.
Summary
Make the repository's pending rename visible to anyone landing on the README or
AGENTS.md. The new name is not yet chosen — it will be picked by the working group via discussion + poll.Changes
README.md:apache-steward→Apache Steward (to be renamed). Surfaces the rename status in every link, GitHub preview, and search-result snippet.> Heads-up — rename in flight, name not yet chosen.blockquote up front:apache/steward— it will be a different, project-agnostic name (the framework stewards multiple ASF project workflows, not just Airflow's).apache/airflow-stewardslug — all path examples in the docs use that slug verbatim. The rename will only change the GitHub repository slug; existing checkouts will keep working with a singlegit remote set-url.AGENTS.md:apache/stewardtarget reference; point at the README heads-up for the candidate list and timeline.doctoc TOC regenerated for
README.md.Test plan
prek run --all-filespassesapache/steward(singular target) references remain anywhere except the heads-up's "notapache/steward" call-out (intentional)🤖 Generated with Claude Code