Jarek, At this point, I don't have a complete understanding of what is being proposed here. I therefore cannot agree to the lazy consensus.
I do believe there is valuable work being done here, but it has moved very quickly and the flurry of emails has left me confused. Is there a composite document outlining what is being proposed? I am especially curious about a few things, since this seems to have grown in a couple of different directions: 1. I assume these projects can grow independently and that the Airflow PMC can at some point choose not to use the Apache Steward work. 2. The security triage and the PR triage work are independent of each other and using one does not preclude or presume the use of the other. 3. The AI skills used for either or additional use cases such as issue triage can be independently expanded by the Airflow PMC without needing changes in Steward. 4. The AI skills can be independently extended for specific providers by the Airflow PMC and/or the steward of the specific provider. Best regards, Vikram Best regards, Vikram On Fri, May 15, 2026 at 7:11 PM Jarek Potiuk <[email protected]> wrote: > Hello Dear community, > > I've been discussing it for a while and I've been busy working > on "apache-steward" repo with a few capable individuals, so I hope > this is not a surprise and I have not seen any objections so far. > > In the PMC's [DISCUSS] thread from 28 April 2026 > ("[DISCUSS] Spinning off Security Triage + PR Triage + Review from > Airflow PMC"): no objections were raised to migrating our triage and > security tooling to a separate PMC, and Jens explicitly agreed it > can and should be shared. > > Since that thread: > > - The new PMC has been renamed from "Apache Steward" to Apache > Magpie (the working repo keeps the `steward` codename). Trademark > feedback drove the rename; the trademark check is filed at > PODLINGNAMESEARCH-252. > - The Top-Level Project Proposal is on cwiki under ASF Private > ("Apache Magpie (former Steward): Top-Level Project Proposal"). > - The repo `apache/airflow-steward` was set up with > `[email protected]` / `[email protected]` > notification targets — i.e. currently under Airflow PMC oversight > pending Magpie's board approval. > - Magpie's establishment is on track for the 20 May board meeting. > > Calling [LAZY CONSENSUS] on the following: > > The Apache Airflow PMC indicates its intent to hand ownership of > `apache/airflow-steward` (the security-issue and PR-management > skill packs, plus the supporting tools) over to the Apache Magpie > PMC at the moment Magpie is established at the 20 May 2026 board > meeting. Airflow continues as a primary downstream user via the > framework's adopter model (project-config overrides + > snapshot-based adoption). Day-to-day Airflow triage workflow is > unchanged; the security tracker (`airflow-s/airflow-s`) and > `[email protected]` channel stay with the Airflow PMC. > > Lazy consensus closes 72 hours from this message — i.e. roughly EOD > Monday 18 May 2026 UTC. Silence = agreement per usual lazy-consensus > convention. Reply with -1 <reason> (or any concern) if you'd like to > adjust scope or discuss further. > > Thanks, > Jarek >
