fedora-ai-ml-sig
MINUTES

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

Meeting started by @jflory7:fedora.im at 16:30:03 UTC

Meeting summary

  1. TOPIC:Roll call & hello's (@jflory7:fedora.im, 16:30:09)
    1. LINK: https://board.net/p/fedora-aiml-sig-meeting-agenda (@jflory7:fedora.im, 16:32:49)
  2. TOPIC:llama.cpp F46 (@trix) (@jflory7:fedora.im, 16:36:34)
    1. INFO: @trix is looking for people interested in maintaining new llama.cpp backends for F46, with priority on vulkan to keep vulkan support in ollama. CI for the unstable backend would also help. (@jflory7:fedora.im, 16:36:38)
    2. HALP: Maintainers needed for new llama.cpp backends, priority on vulkan. Also looking for CI setup help. (@jflory7:fedora.im, 16:36:45)
    3. INFO: Anyone interested in packaging new backends for llama.cpp should reach out to Tom Rix for more info. (@jflory7:fedora.im, 16:43:05)
    4. IDEA: Perhaps later, revisiting the idea of additions to Fedora Packaging Guidelines for AI. Will revisit at a later time. (@jflory7:fedora.im, 16:48:24)
  3. TOPIC:pi-coding-agent in F45/rawhide (@trix) (@jflory7:fedora.im, 16:48:33)
    1. INFO: pi-coding-agent is now in F45/rawhide. @trix is looking for people interested in maintaining and testing non-x86 arches (priority on aarch64), and for folks to hook up other local LLMs and add to the wiki (priority on llama.cpp or lemonade). (@jflory7:fedora.im, 16:48:37)
    2. HALP: Testers and maintainers needed for pi-coding-agent on non-x86 arches, especially aarch64. Also looking for contributors to integrate other local LLMs. (@jflory7:fedora.im, 16:48:43)
    3. LINK: https://fedoraproject.org/wiki/SIGs/AI-ML#pi-coding-agent (@jflory7:fedora.im, 16:57:41)
    4. ACTION: @kannon92 Review and edit the existing `pi-coding-agent` docs on the AI/ML SIG Fedora Wiki page, and coordinate in #ai-ml:fedoraproject.org on changes as needed. (@jflory7:fedora.im, 16:59:38)
  4. TOPIC:#31: Establish a Skills Reviewers sub-team for the skills-library (@jwheel) (@jflory7:fedora.im, 17:00:39)
    1. LINK: https://forge.fedoraproject.org/ai-ml/tickets/issues/31 (@jflory7:fedora.im, 17:00:43)
    2. INFO: Since we discussed #31 two weeks ago, five people raised their hands to join: @cverna, @davdunc, @lbarczio, @cybette, and @ttomecek. @lbarczio also volunteered to draft a human reviewer guide and proposed packaging-focused skills like scratch build fixing and patch backporting. @cverna opened a CI/linting discussion in `ai-ml/skills-library#13`. (@jflory7:fedora.im, 17:01:09)
    3. AGREED: We will create the skills-reviewers team on Forgejo, seed it with @jflory7, @cverna, @davdunc, @lbarczio, @cybette, and @ttomecek, and post an open call on Matrix and Discourse for anyone else who wants to join. The team would get write access to `ai-ml/skills-library` with a lightweight review process. To start, at least one reviewer approval before merge. (@jflory7:fedora.im, 17:08:07)
    4. ACTION: @jflory7 Create skills-reviewer team, then close issue #31. Continue planning/working on Agent Skills in the `ai-ml/skills-library` repo. (@jflory7:fedora.im, 17:08:41)
    5. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2468413 (@jflory7:fedora.im, 17:09:23)
    6. LINK: https://github.com/computerlovetech/agr (@jflory7:fedora.im, 17:10:59)
  5. TOPIC:#34: Scope gpu01 access to ai-packagers-sig and open up ai-ml-sig membership (@jwheel) (@jflory7:fedora.im, 17:13:07)
    1. INFO: I have edited #34 significantly since the last meeting. The title and body are different from what was there before. Please re-read if you looked at it earlier. (@jflory7:fedora.im, 17:13:12)
    2. AGREED: In the short-term, as far as existing/available GPU infrastructure is concerned, the immediate focus for the available hardware is for CI purposes in the F45 release cycle. We commit to following up on the August 13th SIG meeting if there is no new clarity to the hardware access to write something officially. For now, we agree for any requests that come up in the meantime, we will close as `wontfix`, explaining that the GPU hardware is in a "transitionary/exploration" phase while we discover what acceptable use looks like for the Fedora community. (@jflory7:fedora.im, 17:29:14)
    3. IDEA: We will need to think up an Acceptable Use Policy for GPUs, generally however. This is not dependent on having any actual hardware yet. This should be a new ticket. (@jflory7:fedora.im, 17:29:51)
    4. ACTION: @jflory7 Open a new ticket for Acceptable Use Policy discussion, likely targeting Q4 (@jflory7:fedora.im, 17:30:03)
  6. TOPIC:Open floor (@jflory7:fedora.im, 17:30:07)
    1. ACTION: @jflory7 Post a meeting summary of today's meeting on https://discussion.fedoraproject.org (@jflory7:fedora.im, 17:30:31)


Meeting ended at 17:31:02 UTC

Action items

  1. @kannon92 Review and edit the existing `pi-coding-agent` docs on the AI/ML SIG Fedora Wiki page, and coordinate in #ai-ml:fedoraproject.org on changes as needed.
  2. @jflory7 Create skills-reviewer team, then close issue #31. Continue planning/working on Agent Skills in the `ai-ml/skills-library` repo.
  3. @jflory7 Open a new ticket for Acceptable Use Policy discussion, likely targeting Q4
  4. @jflory7 Post a meeting summary of today's meeting on https://discussion.fedoraproject.org


People present (lines said)

  1. @jflory7:fedora.im (120)
  2. @trix:fedora.im (46)
  3. @tflink:fedora.im (18)
  4. @davdunc:fedora.im (17)
  5. @kph1992:matrix.org (15)
  6. @zodbot:fedora.im (11)
  7. @meetbot:fedora.im (3)
  8. @gordonmessmer:fedora.im (3)




Meetbot Logs © 2021-2022 Fedora Websites and Apps Team (Sources)