|
| 1 | +========================== |
| 2 | +Open Source WG: 09/23/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 | +* Megan Knight - Arm |
| 12 | +* Hamza Butt - Arm |
| 13 | + |
| 14 | +* Rod Burns - Codeplay |
| 15 | + |
| 16 | +* Ed Tuke - Imagination Technologies Ltd. |
| 17 | + |
| 18 | +* John Melonakos - Intel |
| 19 | +* Mourad Gouicem - Intel |
| 20 | +* Michael Voss - Intel |
| 21 | +* Timmie Smith - Intel |
| 22 | +* Vasudha Badri-Paul - Intel |
| 23 | +* Alison Richards - Intel |
| 24 | +* Nikolay Petrov - Intel |
| 25 | +* Andrey Fedorov - Intel |
| 26 | + |
| 27 | +* Melissa Aranzamendez - The Linux Foundation |
| 28 | + |
| 29 | + |
| 30 | +Quick Recap |
| 31 | +=========== |
| 32 | + |
| 33 | +The meeting covered the transition plan for CI ownership, including discussions about GitHub administrators, public CI |
| 34 | +resources, and the need for volunteer support from member organizations. Updates were shared about recent leadership |
| 35 | +changes at the API developer summit, with new co-chairs and a language SIG leader appointed. The team reviewed CI |
| 36 | +infrastructure needs across projects and discussed OFAC sanctions compliance requirements, including reporting |
| 37 | +procedures and access permission updates. |
| 38 | + |
| 39 | +Next Steps |
| 40 | +========== |
| 41 | + |
| 42 | +* John to add a paragraph about OFAC sanctions to the security and incident response process documentation. |
| 43 | +* Rod to fix permissions for the security repository to ensure all project owners have access. |
| 44 | +* Megan to share the Linux Foundation document about OFAC sanctions with the mailing list after getting permission from Dolan. |
| 45 | +* Megan to share links to sanction search websites with the meeting notes. |
| 46 | +* Rod to share more detailed CI requirements information with ARM to help them assess their support capabilities. |
| 47 | +* Project teams to review Rod's CI resource estimates and provide feedback on accuracy. |
| 48 | +* Project owners to document a process for reporting potential sanctions violations that includes forwarding to LF Legal within 24 hours. |
| 49 | + |
| 50 | +Summary |
| 51 | +======= |
| 52 | + |
| 53 | +Recap of Dev Summit |
| 54 | +=================== |
| 55 | + |
| 56 | +The group also discussed the recent API developer summit, where Andy and Manuj were introduced as co-chairs, and Biagio |
| 57 | +Costanza took on the role of language SIG leader. |
| 58 | + |
| 59 | +CI Ownership Transition Planning: (`slides`_) |
| 60 | +=============================================== |
| 61 | + |
| 62 | +The meeting discussed the transfer of CI ownership, with Rod presenting slides on the transition plan and highlighting |
| 63 | +the need for GitHub administrators and public CI resources. Megan mentioned that ARM is waiting on requirements to |
| 64 | +assess their involvement, while Rod emphasized the need for volunteers from member organizations to support the |
| 65 | +transition. |
| 66 | + |
| 67 | +Rod presented a detailed analysis of CI resource needs across projects, estimating requirements for CPU and GPU testing. |
| 68 | + |
| 69 | +OFAC Sanctions Compliance: |
| 70 | +========================== |
| 71 | + |
| 72 | +Megan provided an overview of OFAC sanctions compliance requirements, explaining that while projects cannot prevent |
| 73 | +sanctioned individuals from contributing, they must report any concerns to LF Legal. The team discussed existing |
| 74 | +security reporting mechanisms and agreed to update access permissions for relevant documentation. |
| 75 | + |
| 76 | +Project Roundtable |
| 77 | +================== |
| 78 | + |
| 79 | +Projects were surveyed on their current public CI capabilities: |
| 80 | + |
| 81 | +* oneDNN: Public CI is in place with extended coverage using external triggers. |
| 82 | + |
| 83 | + * Performance testing for AArch64, https://github.com/uxlfoundation/oneDNN/actions/workflows/performance-aarch64.yml (Click on "Run Workflow" to open the drop down to see how we can customise the performance testing.) |
| 84 | + |
| 85 | + * Functional testing for AArch64: https://github.com/uxlfoundation/oneDNN/actions/workflows/ci-aarch64.yml |
| 86 | + |
| 87 | +* oneDPL: Public CI using GitHub runners; considering Azure for extended coverage. |
| 88 | +* oneDAL: Public CI is in place with extended coverage using external triggers. |
| 89 | +* oneCCL: <not present> |
| 90 | +* oneMath: CPU testing publicly; exploration of extended testing. |
| 91 | +* oneTBB: Focus on CPU, with internal performance testing. |
| 92 | + |
| 93 | + |
| 94 | + |
| 95 | +.. _`slides`: ../presentations/2025-09-23-UXL-Working-Group-CI-Requirements.pdf |
0 commit comments