---------- Forwarded message --------- From: "Nathalie Chan King Choy (Windows on Arm)" <woa@hub.corecollective.dev> Date: Monday, 20 July 2026 at 07:50:40 UTC-7 Subject: Fwd: [CoreCollective WoA] Notes: 2026-07-14 CoreCollective Windows on Arm Technical on Arm Technical To: Nathalie Chan King Choy (CoreCollective) Cc: CoreCollective Windows on Arm Clarification for following, as far as I can remember: - Omair J. please reply to this message with the first part of your LLVM update, Zoom transcription captured it as “the ROM-side billboards will be moved down to New York” which I am guessing not correct." "Windows on Arm buildbots will be moved to new servers in Linaro Lab" Thanks! -- Omair Javaid www.linaro.org On Wed, 15 Jul 2026 at 20:18, Nathalie Chan King Choy wrote: Hi all, The notes from this week's call are below. Please let us know if you spot any errors or important omissions. Thanks & regards, Nathalie -- CoreCollective Community Manager Android & WoA working groups *Attended:* Gleb K Grant L Jillian B John S Mayank A Nathalie C Omair J Randy L Saket J Thomas D Tyler M *AI Notes - please notify us of inaccuracies:* Meeting Overview - The meeting focused on tracking the enablement of Python packages for Windows on Arm, specifically discussing the strategy for managing the package tracker and addressing unresponsive maintainers. - The team reviewed platform readiness criteria for a regular, non-experimental release and addressed current progress on major blockers like PyTorch and TikToken. - Attendees discussed upcoming RCs for LLVM release Key Decisions Made - [Deferred] The discussion regarding the three package buckets was postponed to two weeks from now due to Anthony being OOO. Mayank & Gleb will be able to attend in 2 weeks. - The team decided to create an additional list or table to track newly enabled packages that fall outside the main tracker's top-1000 parameters. - Wednesday’s WoA Steering Committee call will be canceled if no topics are submitted within the next few hours. Action Items - Omair J. - Omair J. please reply to this message with the first part of your LLVM update, Zoom transcription captured it as “the ROM-side billboards will be moved down to New York” which I am guessing not correct. - Gleb K. - Review the three package buckets once shared and perform preliminary analysis prior to the next meeting. - Mayank A. - Assist with categorizing and segregating the Python package buckets by identifying unresponsive or review-blocked maintainers. - Nathalie C. - Search for an email from Anthony identifying unresponsive package maintainers to assist with bucket categorization. - Distribute the meeting notes. - Include the package buckets to categorize maintainer blockers in the meeting notes. Here they are: - Non-responsive - Does not understand the case - Understands the case but is not interested. For Future - Discussion on package buckets is scheduled to occur in two weeks at next WoA technical call. - The LLVM 23 RCs are expected in a few weeks. Notes Python Package Tracker Strategy - Omair J. suggested expanding the Python package tracking list to include easily buildable packages that natively support Windows on Arm. - Gleb K. explained that the current tracker is primarily based on the top 1,000 downloaded packages, with roughly 10 partner-requested additions. - The team discussed that adding numerous new packages immediately might make progress look stagnant on paper, though expanding the overall enabled count remains highly beneficial. - The new packages aiohttp, safetensors, and ijson have been released on PyPi. - Gleb K. noted in the chat that the list of tracked packages will likely be complete once conda lands. Platform Readiness Assessment - Saket J. noted that Steve Dower at Microsoft is responsible for the Python release and is looking for a general sense of platform readiness rather than a target number of enabled packages. - The WoA Python package readiness is currently estimated to be at 95% plus. - Saket J. recommended reaching out directly to Steve Dower to get his current perspective on the platform's state. Blocker Mitigation and Partner Engagement - PyTorch: Gleb K. found contacts on the Meta side to help coordinate, noting that Microsoft's internal team has been moved off this effort. - TikToken: Gleb K. identified a contact who may be able to reach out to OpenAI. - Anaconda: Gleb K. identified the internal team member coordinating with Anaconda to help align on prioritized blocked packages from the top-1000 list once Anaconda’s infrastructure work is complete. - Large Code Issue: Gleb K. is attempting to track down owners for the issue shared by Omair J. in a previous call and is consulting individuals at Arm for support but not making progress there. - Arm Community Relations: For some of the cases where the maintainer doesn’t understand the value of the WoA patches, Tyler M. clarified that Arm can handle open-source relationship issues on a case-by-case basis via internal contacts and does not require bringing external participants into a WoA technical call. Package Bucketization - Nathalie C. shared the three package buckets in the chat: "Non-responsive", "Does not understand the case", and "Understands the case but is not interested". - Mayank A. confirmed that most of the blocked items previously shared on the CoreCollective WoA mailing list are Python packages and agreed to assist in segregating them into these categories. LLVM Update - The LLVM 23 RCs are expected to release in a couple of weeks, with the Windows 11 release targeted around September 1st.