potiuk opened a new pull request, #60:
URL: https://github.com/apache/airflow-steward/pull/60

   > [!NOTE]
   > **Stacked on top of 
[#57](https://github.com/apache/airflow-steward/pull/57)**, which introduces 
`MISSION.md`. Once #57 merges, this PR's base auto-rebases to `main`.
   
   ## Summary
   
   **`MISSION.md`:**
   
   - Add Paul King (Groovy PMC, Grails PMC, Incubator PMC) to the initial PMC 
roster.
   - Add a *Non-ASF-members* collaborator section listing five contributors who 
will be involved on the project from day one even though they are not (yet) ASF 
Members:
     Bartosz Sławkowski (`@johnslavik`), Yeongook Choo (`@choo121600`), Shahar 
Epstein (`@shahar1`), Vincent Beck (`@vincbeck`), Buğra Öztürk (`@bugraoz93`).
   
   **`.asf.yaml`:**
   
   - Add `@johnslavik` (Bartosz Sławkowski) to the GitHub-collaborators list.
   - The other four (`@choo121600`, `@shahar1`, `@vincbeck`, `@bugraoz93`) are 
already Apache Airflow committers — they have triage rights via the apache org 
through that path; no `collaborators:` slot needed. Left in `.asf.yaml` 
commented out as a record of intent.
   - Add the six non-Airflow-committer ASF members from the PMC roster: 
`@ppkarwasz`, `@zeroshade`, `@andrewmusselman`, `@justinmclean`, `@jbonofre`, 
`@paulk-asert`. Airflow committers on the roster are not listed; they have 
access via the apache org.
   
   **Total active collaborators: 8 of 10**, with headroom for two more without 
an Infra exception.
   
   ## Test plan
   
   - [x] `prek run --all-files` clean
   - [ ] After #57 merges, this PR's base auto-rebases to `main` and the diff 
is unchanged.
   - [ ] On merge, the ASF Infra `.asf.yaml` processor sends 
GitHub-collaborator invitations to the seven new handles; existing 
collaborators (`@andreahlert`) unaffected.


-- 
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]

Reply via email to