|
| 1 | +========================== |
| 2 | +Open Source WG: 08/26/2025 |
| 3 | +========================== |
| 4 | + |
| 5 | +Recording: A recording of the meeting is available in the Linux Foundation https://openprofile.dev/ profile. If you are |
| 6 | +a member of the Working Group you can access this through your account. |
| 7 | + |
| 8 | +Attendees |
| 9 | +========= |
| 10 | + |
| 11 | +* Deepika H V - C-DAC |
| 12 | +* Kuldeep Pal - C-DAC |
| 13 | + |
| 14 | +* Rod Burns - Codeplay |
| 15 | + |
| 16 | +* John Melonakos - Intel |
| 17 | +* Timmie Smith - Intel |
| 18 | +* Alison Richards - Intel |
| 19 | +* Nikolay Petrov - Intel |
| 20 | +* Mourad Gouicem - Intel |
| 21 | +* Vadim Pirogov - Intel |
| 22 | +* Andrey Fedorov - Intel |
| 23 | +* Michael Voss - Intel |
| 24 | + |
| 25 | +* Melissa Aranzamendez - Linux Foundation |
| 26 | + |
| 27 | +* Biagio Cosenza - University of Salerno |
| 28 | + |
| 29 | + |
| 30 | +Quick Recap |
| 31 | +=========== |
| 32 | + |
| 33 | +The meeting focused on the transition of UXL Foundations' engineering infrastructure responsibilities, as Aaron can no |
| 34 | +longer maintain it, with John and Rod reaching out to member companies to gauge interest in taking over these |
| 35 | +duties. Rod presented updates on the current state of CI infrastructure and discussed the need for new hardware hosting, |
| 36 | +GPU testing capabilities, and GitHub organization administrators. The team reviewed project updates and discussed |
| 37 | +upcoming events, including a virtual dev summit and potential face-to-face meeting in Bangalore. |
| 38 | + |
| 39 | +Next Steps |
| 40 | +========== |
| 41 | + |
| 42 | +* Member companies to consider volunteering for GitHub organization administrator roles and email John and Megan if |
| 43 | + interested. |
| 44 | +* Member companies to explore options for providing GPU machines for public CI infrastructure and email John and Megan |
| 45 | + if able to help. |
| 46 | +* Codeplay team to publish documentation for CI infrastructure handover. |
| 47 | +* John to update the working group README with current project milestones. |
| 48 | +* Project leads to update their project milestone pages for John's reference. |
| 49 | +* John to reach out to member companies individually about transferring CI infrastructure responsibilities. |
| 50 | +* Project teams to consider promoting the upcoming virtual dev summit on September 17th to their networks. |
| 51 | + |
| 52 | +Summary |
| 53 | +======= |
| 54 | + |
| 55 | +UXL Infrastructure Transfer Discussion: (`slides`_) |
| 56 | +======================================= |
| 57 | + |
| 58 | +The meeting discussed the transfer of UXL Foundations' engineering infrastructure responsibilities, as Aaron is no |
| 59 | +longer able to maintain it. John and Rod shared that they are reaching out to member companies to gauge their interest |
| 60 | +and capacity to take on this responsibility. Rod presented slides to outline the current state of the CI infrastructure |
| 61 | +and planned to discuss further details with the team. |
| 62 | + |
| 63 | +CI Infrastructure Transition Challenges: |
| 64 | +======================================== |
| 65 | + |
| 66 | +Rod discussed the current state of CI (Continuous Integration) for the foundation's repositories. He explained that |
| 67 | +while some basic CI exists, primarily in Intel's infrastructure, the goal is to have public CI that can validate |
| 68 | +projects independently. Rod mentioned that projects have listed their CI requirements on a GitHub page and that a |
| 69 | +tracking board exists for open CI-related items. He also noted that Aaron has been the administrator for the GitHub |
| 70 | +organization and has been working with Codeplay to document CI setup and establish infrastructure. However, Rod revealed |
| 71 | +that Codeplay can no longer continue these activities, as Aaron is no longer able to act as the admin, and Robert has |
| 72 | +stepped back from his roles in the steering committee and as a spec editor. |
| 73 | + |
| 74 | +Hardware and CI Resource Changes: |
| 75 | +================================= |
| 76 | + |
| 77 | +Rod discussed the changes in available hardware and CI resources, noting that Intel's Tiber cloud and GPU Max machines |
| 78 | +are no longer accessible. He emphasized the need to find new ways to host hardware for various projects, secure |
| 79 | +workflows, and maintain a knowledge base. Rod highlighted the importance of GPU testing capabilities, which are |
| 80 | +currently missing, and called for contributions to add runners and hardware. The team is seeking organizations or |
| 81 | +individuals to help with these activities moving forward. |
| 82 | + |
| 83 | +Public CI Infrastructure Transition Plan: |
| 84 | +========================================= |
| 85 | + |
| 86 | +Rod discussed the transition of public CI infrastructure and the need for GitHub organization administrators. He |
| 87 | +emphasized the importance of finding a new owner for establishing public CI and sourcing GPU machines for testing. Rod |
| 88 | +also explained the roles and responsibilities of GitHub repository administrators, including managing user permissions |
| 89 | +and security incident reports. He called for volunteers to help with these tasks and encouraged members to apply for |
| 90 | +additional CI resources through the Linux Foundation or other providers. |
| 91 | + |
| 92 | +Infrastructure Changes and Workflow Impact: |
| 93 | +=========================================== |
| 94 | + |
| 95 | +The team discussed infrastructure changes and their impact on workflows. Rod confirmed that most removed experimental |
| 96 | +projects were not in active use, and the only ongoing project using their infrastructure is the oneDNN project, which |
| 97 | +runs tests on separate machines and posts results publicly. Hamza explained that while some projects use ARM runners, |
| 98 | +Github now offers public ARM runners on their cobalt platform, though these are not guaranteed to have specific |
| 99 | +architectures and have had recent issues with Microsoft's architecture changes. |
| 100 | + |
| 101 | +Centralized Infrastructure Planning Discussion: |
| 102 | +=============================================== |
| 103 | + |
| 104 | +The group discussed the need for a centralized infrastructure to support their projects, with John emphasizing that it |
| 105 | +should be customer-driven and coordinated by a central body. Hamza and Rod clarified that the long-term plan involves |
| 106 | +shared resources that projects can access, though the exact implementation details are still being worked out. John |
| 107 | +requested that other member companies volunteer to help host projects and that attendees take the initiative to |
| 108 | +coordinate infrastructure within their organizations. |
| 109 | + |
| 110 | +Project Updates and Backend Progress: |
| 111 | +===================================== |
| 112 | + |
| 113 | +The team reviewed updates across various projects. Nikolay mentioned no specific updates for his project, while John |
| 114 | +planned to update the working group's README and milestone information. Andrey reported that the ARM CPU backend was |
| 115 | +enabled for the SFT domain and an RFC was opened to support the OpenBLAS backend. Mike shared that they were working |
| 116 | +towards their next release with a code freeze approaching, which would include an improved tasking API. Timmie also |
| 117 | +reported progress, mentioning their upcoming milestone with additional range-based APIs and improved algorithm |
| 118 | +performance. |
| 119 | + |
| 120 | +Virtual Dev Summit Planning Discussion: |
| 121 | +======================================= |
| 122 | + |
| 123 | +The team discussed an upcoming virtual dev summit on September 17th, featuring a keynote from Fujitsu and other |
| 124 | +presenters. Alison encouraged everyone to register and share the event with their communities, noting that UXL has a |
| 125 | +newsletter and social media presence for outreach. John inquired about community communication methods, and Alison |
| 126 | +mentioned the UXL newsletter and web/social media channels. The team also briefly discussed plans for a face-to-face |
| 127 | +event in Bangalore in Q4, with Megan working on the details. |
| 128 | + |
| 129 | + |
| 130 | + |
| 131 | +.. _`slides`: ../presentations/2025-08-26-UXL-Working-Group-CI-Transition.pdf |
0 commit comments