#meeting-2:fedoraproject.org: fedora-ai-ml-sig

Meeting started by @tflink:fedora.im at 17:30:22 UTC

Meeting summary

  1. TOPIC:FESCo ticket about using AMD's llvm fork for hipcc (@tflink:fedora.im, 17:33:50)
    1. LINK: https://pagure.io/fesco/issue/3291 (@tflink:fedora.im, 17:33:57)
    2. INFO: the FESCo ticket wasn't so much for permission as for guidance and so far, the guidance seems to be a somewhat OK with requests for more justification and submission as a feature for the bundling change (@tflink:fedora.im, 17:38:31)
    3. INFO: at this moment, the plan is to start bundling AMD's llvm fork with hipcc for ROCm 6.3 (@tflink:fedora.im, 17:42:53)
  2. TOPIC:HW testing ideas/proposals/requirements (@tflink:fedora.im, 17:44:08)
    1. INFO: at the last meeting, there was some conversation around automated testing and after some chaos and confusion, the decision was to start gathering ideas, requirements etc. for later discussion (@tflink:fedora.im, 17:44:45)
    2. LINK: https://board.net/p/fedora-ai-ml-sig-testing-brainstorm (@tflink:fedora.im, 17:44:48)
    3. INFO: the following topics are the proposals that were part of that document (@tflink:fedora.im, 17:46:22)
  3. TOPIC:Basic Kernel Testing (@tflink:fedora.im, 17:46:28)
    1. INFO: the proposal is have a setup for automating kernel testing on bare metal, focusing on the driver bits that affect the ai-ml bits we're working on (@tflink:fedora.im, 17:51:24)
  4. TOPIC:ROCm Component Testing (@tflink:fedora.im, 17:51:54)
    1. INFO: the proposal is pretty simple, start with containers and run ROCm component tests whenever the components or their dependencies change (@tflink:fedora.im, 17:54:26)
  5. TOPIC:End to End ML Testing (@tflink:fedora.im, 17:57:54)
    1. INFO: the proposal is to help hedge against the fragility of ML stacks by creating Fedora-based containers for those environments and run pseudo-production workloads through those containers on a regular basis (@tflink:fedora.im, 18:04:04)
  6. TOPIC:LLM Training (@tflink:fedora.im, 18:09:06)
    1. INFO: the idea here is to train some LLM model from scratch using the tools we have available to us (@tflink:fedora.im, 18:09:28)
    2. INFO: this poses many challenges, including access to sufficient hardware and potential licensing issues (@tflink:fedora.im, 18:10:07)
  7. TOPIC:next steps for testing projects/conversations (@tflink:fedora.im, 18:14:26)
  8. TOPIC:Proposed General Requirements (@tflink:fedora.im, 18:15:14)
    1. INFO: the idea here was to start describing some of the general things that we want to encourage or avoid (@tflink:fedora.im, 18:15:34)
  9. TOPIC:next steps (@tflink:fedora.im, 18:20:21)
    1. INFO: tflink, trix and man2dev will write up brief proposals detailing what they want to see happen before the next meeting where we can discuss the proposals more as a group (@tflink:fedora.im, 18:29:59)
    2. INFO: proposals need to be in a non-matrix format; wiki or discourse is encouraged (@tflink:fedora.im, 18:30:23)
  10. TOPIC:next meeting date (@tflink:fedora.im, 18:32:06)
    1. INFO: the next two ai-ml-sig meetings (2024-12-19 and 2025-01-02) are canceled. The next ai-ml-sig meeting will be on 2025-01-16 (@tflink:fedora.im, 18:34:44)
    2. INFO: if there are topics to discuss, folks are around on discourse and matrix (@tflink:fedora.im, 18:35:05)
  11. TOPIC:open floor (@tflink:fedora.im, 18:35:10)


Meeting ended at 18:37:16 UTC

Action items

  1. (none)


People present (lines said)

  1. @tflink:fedora.im (127)
  2. @trix:fedora.im (53)
  3. @man2dev:fedora.im (24)
  4. @wbclark:fedora.im (5)
  5. @zodbot:fedora.im (4)
  6. @meetbot:fedora.im (2)