fedora-ai-ml
MINUTES

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

Meeting started by @tflink:fedora.im at 16:30:57 UTC

Meeting summary

  1. TOPIC:previous meeting follow-up (@tflink:fedora.im, 16:33:04)
    1. LINK: https://pagure.io/fedora-ai-ml (@tflink:fedora.im, 16:34:59)
    2. LINK: https://pagure.io/fedora-ai-ml/issue/1 (@tflink:fedora.im, 16:35:44)
  2. TOPIC:proposal for a chatbot project (@tflink:fedora.im, 16:39:07)
    1. ACTION: @damaestro to scope a phase one for a chatbot to ask questions about fedora using fedora (@jsteffan:fedora.im, 17:03:25)
  3. TOPIC:status check on F41 features (@tflink:fedora.im, 17:04:22)
  4. TOPIC:Improving Testing (@tflink:fedora.im, 17:14:56)
    1. IDEA: this question should be answered correctly by a phase 1 chatbot (@jsteffan:fedora.im, 17:24:05)
    2. IDEA: this question should be answered correctly by a phase 1 chatbot: is there a fedora bot thing that could at least build cpu torch and its dependencies.. then run some cpu torch example/tests ? (@jsteffan:fedora.im, 17:24:35)
    3. ACTION: investigate fedora CI for running automated pytorch suite CPU testing (@jsteffan:fedora.im, 17:26:26)
  5. TOPIC:pings before meeting time (@tflink:fedora.im, 17:28:22)
    1. LINK: https://pagure.io/fedora-ai-ml/issue/10 (@tflink:fedora.im, 17:28:29)
    2. INFO: agreed that pings to the matrix room before meetings could help and at least wouldn't be a problem. we can re-asses in the future if needed (@tflink:fedora.im, 17:32:02)
  6. TOPIC:open floor (@tflink:fedora.im, 17:32:14)


Meeting ended at 17:38:22 UTC

Action items

  1. @damaestro to scope a phase one for a chatbot to ask questions about fedora using fedora
  2. investigate fedora CI for running automated pytorch suite CPU testing


People present (lines said)

  1. @tflink:fedora.im (85)
  2. @ludiusvox:fedora.im (46)
  3. @jsteffan:fedora.im (40)
  4. @man2dev:fedora.im (26)
  5. @trix:fedora.im (21)
  6. @zodbot:fedora.im (3)
  7. @meetbot:fedora.im (2)