---------- Forwarded message ---------
From: Nathalie Chan King Choy
Date: Tuesday, 19 May 2026 at 09:40:43 UTC-7

Hi all,

Please let us know if you spot any errors or important omissions.

NOTE:

Later this week I'll update the meeting series to use Zoom. Please keep an eye out for that calendar update.

Thanks & regards,

Nathalie

CoreCollective Community Manager

Android & WoA working groups

Next OOO: May 25th, 2026

Attended:

David Whaley

Evgeny Karpov

Gleb Khmyznikov

John Stubley

Julianus Larson

Maxim Kuvyrkov

Mayank Agrawal

Nathalie Chan King Choy

Omair Javaid

Saket Jha

Tamas Petz

Tom Dunkle

Gemini notes:

Next steps

[Gleb Khmyznikov] Share Package List: Provide the list of Python packages missing from distribution tools to the team.
[Nathalie Chan King Choy] Update Mailing List: Add Evgeny to the core collective WoA mailing list.
[Evgeny Karpov] Clarify Compiler Needs: Determine if cross-compilation for Windows on Mac and x64 hosts is required for library owners.
[WoA SC] Discuss Repository Setup: Discuss during the steering committee meeting the establishment of a repository for external developers to communicate with WoA WG & to provide CI visibility. Do we want an email alias in addition to the repo? Consult with Mike to determine ownership and setup requirements for the new external communication repository.

Python support updates and CI enablement: Gleb Khmyznikov provided updates on Python development, highlighting a GitHub blog post regarding official support for GitHub runners and the resolution of the Python action issue. To restore cryptography support, Gleb Khmyznikov worked with two maintainers to enable it with "zero commitments," ensuring that build or test failures would not disrupt release cycles. Additionally, Gleb Khmyznikov noted that the enablement pace dropped by 50% over the last six months, a result expected by the group as the low-hanging fruit has already been addressed.
Evaluation of Python package funding and infrastructure: Omair Javaid, who evaluated the Python packages list on behalf of Linaro, identified a recurring issue regarding the lack of CI or commitment for CI for various packages. Omair Javaid raised a query to the core collective regarding the funding of infrastructure when maintainers are unwilling to invest the necessary engineering hours and suggested the possibility of providing GitHub resources to bridge these gaps. Gleb Khmyznikov confirmed they are attempting to solve this by partnering with Anaconda, as they have shown willingness to host packages and fill these gaps within their own infrastructure.
Availability of Python packages and collaboration needs: Gleb Khmyznikov explained that while many blocked packages are buildable locally, they lack official distribution channel support, and building dependencies in CI cycles is inefficient for others. The team is currently working with the Python Package Index to enable support for these packages, though availability remains limited. Omair Javaid requested a comprehensive list of packages that are inaccessible across all management tools to prioritize the most critical blockers, which Gleb Khmyznikov agreed to provide alongside the list of packages they have already asked Anaconda to support.
Strategies for remaining Python blockers and upstreaming: Gleb Khmyznikov clarified that remaining packages are generally blocked by cloud or library dependencies rather than technical build failures. David Whaley noted that ARM had team members utilizing tools like Codex and Co-pilot to build packages (wheels) and perform smoke tests, suggesting that the primary challenge is the outreach and upstreaming process. David Whaley proposed repurposing LLVM resources to assist with this upstreaming effort, as they have reached a point where the LLVM work is largely stabilized.
Steering committee coordination for resource reallocation: David Whaley committed to bringing the proposal to repurpose LLVM resources for Python support to the upcoming steering committee meeting. Nathalie Chan King Choy confirmed that a meeting poll had been sent to David Whaley and Andy to coordinate Arm-Linaro discussion, with the group agreeing to ensure Andy is included in the call.
GCC enablement and CI migration updates: Evgeny Karpov provided an update on the GCC enablement, noting that the migration to ARM 64 Linux and Windows standard runners for internal CI is complete, with ARM 64 showing better performance than x 64. Evgeny Karpov noted this work establishes the foundation for a public repository for weekly builds for Minimalist GNU for Windows and GCC. The team is currently investigating the necessary patch contributions to ensure these repositories remain upstream-compliant.
Communication and architectural planning for GCC: Evgeny Karpov requested to be added to the core collective email list and opened a discussion on whether to build cross-compiler toolchains for Minimalist GNU for Windows on Mac and x 64 hosts to support library owners without ARM 64 access. Gleb Khmyznikov and Evgeny Karpov discussed the necessity of these extra targets given existing cloud environments, and Evgeny Karpov confirmed that users will be able to report feedback through the upcoming public GitHub repository.
LLVM release update: Omair Javaid announced that LLVM version 22.1.6 has been released and the installer is now available on the official repository.
Establishing public communication channels and repositories: The group discussed the logistics of setting up a repository or email alias for external communication and tracking CI results. Gleb Khmyznikov advocated for using a GitHub repository for better transparency and tracking, suggesting that all engineers in the core collective be added as members. The group agreed to finalize the ownership and setup of this repository, potentially under the existing core collective GitHub organization, during the next steering committee meeting, with Nathalie Chan King Choy planning to coordinate offline with Mike.