Thanks for the update, this sounds great! I just wanted to clarify the naming/migration path: are we moving to apache/steward (instead of apache/magpie), and is the intended flow something like apache/airflow-steward --> apache/steward --> apache/magpie? Just want to make sure I fully understand the direction.
Best, Yeonguk On 2026/06/02 11:25:15 Jarek Potiuk wrote: > Hello here, > > I reached out to Sander yesterday, and I will try to move the "board" > discussion forward today. However, I would also like to complete some > overdue renames today. > > We have just a few outstanding PRs left. I will merge them now, even if > they aren't fully complete to avoid costly conflict resolution; we will > continue iterating on those. > > This will help us with a more global rename, implementing the upgrade, and > preparing for moving out to "apache/steward" finally. > > I've been quite focused on ground-level tasks over the last weekâfocusing > on "ironing out wrinkles" in the existing skills - those we are "actively" > using. I implemented several of those "infrastructural" issues I found > across the **three** projects where Magpie is integrated: > > *a)* airflow -> PR triage is used heavily there > *b)* airflow-s -> Our security issues > *c)* security -> I am running a campaign to scan ASF projects with LLM > security and preparing them for scan and I adopted Magpie (and Magpie's > approach) there for privacy/security > > A lot of friction has been removed. I generalised the security part, added > many optimizations for both user workflow and token usage (the Security > family of skills now uses about 5x fewer tokens). I also nicely integrated > the two official "Ponymail" and "Apache Projects" MCPs from comdev. I also > added more security layers and privacy layers and optimized a lot a number > of "interruptions" running some of the skills involved. > > So .. I think now is a good time to do the renames :) > > Kind request .. Hold on with new changes ;) > > J. >
