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

   ## Summary
   
   Two changes landed together (one commit; happy to split if reviewers prefer):
   
   ### 1. Add Calvin Kirs to the ASF-members roster
   
   Calvin got back to me saying yes — adding him alongside the other late 
additions (Ismael, tison, James). New line:
   
   \`\`\`
   - Calvin Kirs (kirs) — Doris PMC, Geode PMC
   \`\`\`
   
   ### 2. Add Apache LDAP IDs in parentheses for every roster entry
   
   Now that the Board resolution is two days out, the roster needs to be 
unambiguously linked to ASF identity. Format mirrors common ASF roster 
conventions:
   
   \`\`\`
   - <Full Name> (<apache-id>) — <PMC list>
   \`\`\`
   
   ## IDs that need a quick confirmation in review
   
   All IDs were derived from the @apache.org email each member uses, with two 
best-guess exceptions:
   
   - **Calvin Kirs → \`kirs\`** — Calvin, please confirm. Alternative guesses 
if wrong: \`calvinkirs\`, \`ck\`.
   - **Justin Mclean → \`jmclean\`** — Justin, please confirm. You primarily 
use \`[email protected]\`; if the ASF ID is something different, flag it 
here.
   
   Everyone else's ID is the prefix of their published \`@apache.org\` address 
and should be correct, but anyone who spots a mistake on their own line — 
please call it out and I'll fix in a follow-up.
   
   ## What this PR does **not** touch
   
   Same \`.asf.yaml\` cap caveat as #138 / #140: the collaborators block is at 
the ASF Infra cap of 10 entries (bumping requires a [email protected] 
request). Leaving as-is.
   
   ## Test plan
   
   - [x] \`prek run --files MISSION.md\` clean
   - [ ] Calvin Kirs confirms \`kirs\` as his ASF LDAP ID
   - [ ] Justin Mclean confirms \`jmclean\` as his ASF LDAP ID
   - [ ] Visual review of the 16-line roster
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


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