---------- Forwarded message --------- From: "Nathalie Chan King Choy (Windows on Arm)" <woa@hub.corecollective.dev> Date: Tuesday, 2 June 2026 at 09:31:50 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 Don Harbin Evgeny Karpov Gleb Khmyznikov Grant Likely Julianus Larson Nathalie Chan King Choy Paul Black Randy Linnell Saket Jha Sudipto Paul Tamas Petz Links shared in chat: - https://github.com/CoreCollective-dev/windows-on-arm-wg - https://github.com/khmyznikov/PyEnv-WoA-State/actions/ workflows/monitor_cryptography_ci.yml <https://github.com/khmyznikov/PyEnv-WoA-State/actions/workflows/monitor_cryptography_ci.yml> - https://github.com/bitsandbytes-foundation/bitsandbytes/pull/1959 Zoom AI notes: Quick recap The meeting focused on the establishment of a new Windows on ARM Core Collective Working Group and updates on Python enablement efforts. Nathalie introduced a new GitHub repository created for issue tracking, and the group discussed including Linaro as an active member since they are running the core collective forum backend. Gleb provided updates on Python package enablement, including a trial period for cryptography packages and noting that NVIDIA has similar dependencies on Python as Qualcomm, so recruiting NVIDIA to CoreCollective might help with additional Python package support. Anthony reported that most Python packages in the list for the Microsoft-Linaro SOW face community issues rather than technical challenges, with unresponsive maintainers being the primary obstacle. Evgeny updated the group on GCC cross-compiler development, noting that patches have been upstreamed and a public repository should be published within the month. The LLVM representative did not have updates to share, and the conversation ended with discussions about potential future NVIDIA-related requests for CUDA enablement. Next stepsAnthony - Post detailed review and status updates of Python packages (including rationale for dropping packages with viable alternatives) as comments on the relevant ticket, and notify Gleb of packages that can be marked as resolved due to alternatives. - For packages under company maintenance, contact relevant company support channels to request review/merge of outstanding pull requests for Windows on ARM support. Evgeny - Publish the public GCC cross-compiler repository and landing page, and add the link to the Core Collective repository for issue reporting. Gleb - Move the existing Windows on ARM cryptography monitoring action (CI checks and issue creation) to the Core Collective repository once access is granted. - Share contacts from NVIDIA's Python/Onyx Runtime team with Nathalie to facilitate their invitation to the Core Collective forum. - Mark Python packages in the tracking list as resolved/dropped when provided with information about viable alternatives from Anthony. - Ask Lisa from his team to join the next meeting (or prepare information) to discuss potential CUDA-related enablement requests from NVIDIA. Nathalie - Add Linaro as an explicit active member to the Core Collective Working Group repository and update the member list accordingly. - Investigate and set up GitHub repository member invites, and invite relevant participants (including Gleb) to the new Windows on ARM Core Collective Working Group repository. Randy - Meet with NVIDIA at conference to introduce them to Core Collective and encourage their participation. Collaboration - Saket/Gleb: Follow up offline to confirm if any CUDA-related enablement requests from NVIDIA (via Microsoft) are anticipated, and communicate findings to the group. Summary Windows on ARM Working Group Nathalie created a new Windows on ARM Core Collective Working Group repository and shared it with the team during the meeting. The group discussed adding Linaro as an active member to the repository, with Grant confirming it was appropriate to include them. Gleb shared his current monitoring setup for cryptography testing and suggested moving it to the new Core Collective repository if they decide to support it. The team agreed on the importance of having volunteers and engineers participate in maintenance work by creating and assigning issues as needed. Python Enablement Strategy Discussion The team discussed Python enablement efforts for Windows and ARM, with Gleb reporting on cryptography package trials and a NVIDIA interest in Python packages. Anthony reviewed the list of Python packages in the Microsoft-Linaro SOW, finding that most issues are maintainers not responding rather than technical challenges, with many packages being poorly maintained or having viable alternatives available. The team agreed to review each package individually to determine which ones to pursue further, with Anthony planning to document his findings in a ticket comment and potentially reaching out directly to companies that maintain these packages. Cross-Compiler Development Progress Update Evgeny reported that the team has successfully identified and upstreamed patches needed to build a cross-compiler from upstream repositories, with internal CI that can make daily or weekly releases already in place. The public repository is ready but not yet published, with plans to make it available for Linux and potentially macOS this month. After publishing the public repository, the team will proceed with upstreaming patches related to relocations and then work on native toolchain development. LLVM Paul Black, representing the LLVM team, had no updates to share. CUDA Enablement Discussion Anthony discussed pending CUDA enablement for Blender, but noted that pull requests are on hold until NVIDIA's SDK becomes publicly available. Gleb agreed to follow up with Lisa in his team who works closely with NVIDIA to provide clarity on whether they anticipate receiving any CUDA-related requests from NVIDIA or Microsoft.