potiuk opened a new issue, #523: URL: https://github.com/apache/airflow-steward/issues/523
Apache Magpie was established as a Top-Level Project by Board resolution on **2026-06-17**. This issue is the master tracking checklist for everything that has to happen now to actually stand the project up — Infra resources, governance/PMC setup, project identity, IP clearance, the first release, and migrating off the legacy `airflow-steward` identity. Sub-issues exist for some items and are linked inline; this issue is the umbrella. ## 1. Governance & PMC setup - [ ] File the establishing Board resolution and chair appointment in Foundation records - [ ] Record the PMC roster in Whimsy / `committee-info.txt` (creates the `magpie` LDAP group) - [ ] Confirm chair (Jarek Potiuk) registered as VP, Apache Magpie with the Secretary - [ ] Enroll Magpie in the Board reporting cycle (monthly for first 3 months, then quarterly) via the Reporter tool - [ ] Add the named day-one collaborators as committers once accounts exist ## 2. Infrastructure — mailing lists - [ ] Establisjh magpie as a PMC - [ ] Create `[email protected]` - [ ] Create `[email protected]` - [ ] Create `[email protected]` - [ ] Decide on and create any additional lists (`notifications@`, `issues@`, `users@`) as needed - [ ] Set moderators for each list - [ ] Confirm list archives are flowing to lists.apache.org / PonyMail - [ ] **Move the existing discussion list** to `[email protected]` — announce the move, port subscribers, set up redirect/forwarding from the old venue - [ ] Subscribe current participants and post a kickoff/orientation message to `dev@` ## 3. Infrastructure — source control & GitHub - [ ] Rename `apache/airflow-steward` → `apache/magpie` (or create `apache/magpie` and migrate), with redirect from the old slug - [ ] Update `.asf.yaml` for the new repo (features, notifications, branch protections) - [ ] Sync GitHub team permissions from the `magpie` LDAP group via GitBox - [ ] Confirm GitHub Issues enabled and label taxonomy carried over - [ ] Repoint commit/PR notifications to `commits@` / `notifications@` - [ ] Sweep the codebase and docs for remaining `airflow-steward` references and update to `magpie` (README heads-up note can then be removed) ## 4. Project identity, website & branding - [ ] Logo for Magpie — tracked in #243 - [ ] Website for Magpie — tracked in #244 - [ ] Provision DNS / publishing for `magpie.apache.org` (site repo, `.asf.yaml` staging+publishing, CNAME) - [ ] Add the website pages ASF policy requires (Home, Downloads, License, Security, Privacy, Thanks, Sponsorship/Donate, Apache branding/trademark attribution) - [ ] Create the project DOAP file so Magpie appears on projects.apache.org - [ ] Trademark/brand review with VP Brand Management — register "Apache Magpie" ? (probably not yet), confirm compliant naming, add a trademarks page - [ ] Set up the project entry in projects.apache.org metadata (category, descriptions, PMC, repos) - done by DOAP ## 5. Communications - [ ] Announce establishment on `[email protected]` - [ ] ASF blog post / press coordination with VP Marketing & Publicity - [ ] Social media announcement via ASF channels - [ ] Set up the project Slack channel on the-asf Slack (`#magpie`) - [ ] Update GitHub repo description, topics, and pinned links to point at the new identity ## 6. IP clearance & licensing - [ ] Confirm no Software Grant Agreements are required (ASF-owned source) and document that determination - [ ] Verify LICENSE / NOTICE / SPDX headers are correct repo-wide for the renamed project - [ ] Confirm dependency license compatibility audit is current ## 7. Project bootstrap (from MISSION Initial Goals) - [ ] Confirm project skeleton, CI, and contributor docs are in place under the new identity - [ ] Decide on project family taxonomy approach - discussed in https://lists.apache.org/thread/rckckmc50hl3z33yxz5rkszs1k7gf5w5 - [ ] Verify the privacy & security posture as a release-blocking part of v1 - [ ] Ship the maintainer-education stream (pattern catalogue, "your first skill" path, first workshops) alongside v1 - [ ] Validate vendor-neutrality across the v1 pilots (frontier / local / Apache-aligned backends) ## 8. Release infrastructure & first release - [ ] Create `dist.apache.org` space for Magpie - [ ] Establish project KEYS file and ensure PMC release managers' keys are in it - [ ] Document the release process (matching ASF release policy) in the repo - [ ] Set up `downloads`/release-distribution config and the download page - [ ] Cut the first Apache release through the standard process (target: within 3 months of resolution), with artefacts usable by non-ASF adopters -- 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]
