---------- Forwarded message --------- From: "Nathalie Chan King Choy (Windows on Arm)" <woa@hub.corecollective.dev> Date: Tuesday, 21 April 2026 at 09:12:29 UTC-7 Hi all, Please let us know if you spot any errors or important omissions. Thanks & regards, Nathalie -- CoreCollective Community Manager Android & WoA working groups Attended: Anthony Roberts David WHaley Gleb Khmyznikov Lina Iyer Marcus Perryman (returns from sabbatical 20th July) Maxim Kuvyrkov Mayank Agrawal Nathalie Chan King Choy Omair Javaid Saket Jha Tom Dunkle Gemini notes: Next steps - Gleb Khmyznikov] Track Python Velocity: Create progress graphic (burndown chart) showing Python enablement velocity. Sort the enablement table prioritizing active/blocked libraries at the top. - [Tom Dunkle] Decide IFS Status: Determine if the IFS library should be officially added to the Top 1000 tracking list. - [David Whaley] Secure Engineers: Investigate options for securing additional engineering resources for Python package work. (maintaining as opposed to more packages) - [Omair Javaid] Investigate PDBs: Figure out what is wrong with the current LLVM process preventing PDB files from being generated. - [Omair Javaid, Marcus Perryman] Discuss Symbol Publishing: Schedule a 1-on-1 meeting to discuss adding LLVM symbol publishing to the backlog after PDB generation is fixed. - [Tom Dunkle] Chase GCC Update: Follow up with Andre to obtain an update on the GCC status. - [Gleb Khmyznikov] Resume Cryptography: Continue conversation with cryptography maintainers after the GitHub team releases the new Windows on ARM images. Details - Introduction of Core Collective Leadership Changes: Marcus Perryman is transitioning out as the working group chair due to an upcoming sabbatical, with Saket Jha taking over the chair role. Nathalie Chan King Choy has joined the group to support them as the community manager . The core collective work direction for Windows and ARM will not change, focusing on key priorities like Python libraries, compilers, and continued enablement and unblocking . - Updates on Python Library Enablement: Gleb Khmyznikov reported ongoing work from Qualcomm, sharing a link that shows current progress, noting that several pull requests have been opened and some have already been merged, resulting in good coverage for a key table . Gleb Khmyznikov also mentioned they are still in contact with the GitHub team regarding image releases, which, once resolved this week, should allow work to resume with cryptography maintainers to unblock that package . - Request for Visual Progress Tracking for Python Libraries: Marcus Perryman requested that Gleb Khmyznikov update the Python library tracking table to include a visual progress report, such as a burndown graph, to better track the velocity of enablement . It was also suggested to sort the table to prioritize items marked as red or blocked at the top, moving completed (green) items to the bottom to focus efforts . - Clarification on Python Enablement Goals: Saket Jha inquired if all libraries marked red on the tracking table were considered "must-haves" for the October release, to which Marcus Perryman clarified that the primary goal is hitting a top 1,000 library target, which is an overall number target rather than a strict dependency target . The goal is to ensure the top 1,000 most popular Python packages are available by October to satisfy press scrutiny and demonstrate ecosystem readiness . - Discussion on Including an Additional Python Library (IFS): Marcus Perryman asked Tom Dunkle about the status of the IFS library, noting it was brought up by the Appashure team but is not currently on the top 1,000 list. Tom Dunkle confirmed they are not actively working on it but are aware it is being worked on upstream, and they accepted ownership to decide whether to add it to the tracking list . - Python as Top Priority for October Release: David Whaley raised the point of Python being the top priority for the group, a sentiment Marcus Perryman affirmed due to the importance of exiting Python's experimental status in October, which is critical for ARM's relevance in the developer ecosystem, particularly with the industry's focus on AI and machine learning . Marcus Perryman confirmed that the gatekeeper, Steve Daer, is looking for a "sense of readiness," which they believe can be demonstrated by hitting the top 1,000 packages and having Anaconda ready. - Discussion on Need for Additional Python Engineering Resources: In response to a discussion about whether additional engineering resources are needed, Gleb Khmyznikov stated that if Qualcomm maintains their current effort, they do not need more people for mass enabling libraries, but they would benefit from an engineer for ongoing maintenance work, such as investigating test failures. David Whaley confirmed they would look into resourcing based on this feedback . - GCC Compiler Updates: The GCC topic was briefly discussed, but the usual reporting members were not present at the meeting. Tom Dunkle volunteered to follow up with Andre, who previously provided updates, to see if they could get an update for the next meeting . - LLVM Release and PDB Generation Status: Omair Javaid provided a status update for LLVM, noting that release 22.1.4 has been uploaded and things are stable . Marcus Perryman followed up on the ongoing request for PDB files for LLVM release builds, which Omair Javaid acknowledged is currently blocked due to errors encountered during attempts to break down and run the release script, requiring further investigation into configuration issues and race conditions . - Motivation and Goal for LLVM PDB Generation: Marcus Perryman explained the motivation for needing the PDB files is to perform performance analysis on LLVM on Windows to identify potential PGO optimization improvements, targeting an estimated 5% performance gain . They also emphasized that having PDB files available for every Windows ARM release would be hugely valuable to the community, suggesting the feature be added to the backlog for LLVM work, subject to Saket Jha's funding approval . - Updates on FFmpeg and V8 Forks: Marcus Perryman shared updates from Qualcomm, noting they have forked the FFmpeg project and created a repository for building ARM 64EC bits after the upstream team rejected the work . They also confirmed Qualcomm has a V8 port, and a near-full Chromium port, for ARM 64EC, though both are forks and not upstreamed, prompting questions about the handling and performance of compiled assembly in these ports . - Update on Cryptography Blockers: Tom Dunkle requested a recent update on cryptography, which Gleb Khmyznikov addressed by reiterating that they are waiting for new Windows and ARM images on GitHub from the GitHub team, which is expected this week, before resuming conversation with cryptography maintainers . You should review Gemini's notes to make sure they're accurate.