Hey folks!
Here is the summary of the 2026-10-08T16:30:00Z→2026-10-08T17:30:00Z AI/ML SIG meeting.
The AI/ML SIG maintains and advances AI/ML tooling, frameworks, hardware enablement, and more across Fedora. Today’s meeting focused on administrative votes for chat automation, tracking ROCm 10.1 package builds in Copr, scoping beginner-friendly user guides, and evaluating a proposed migration from the Fedora Wiki to Fedora Docs.
Topics discussed in this meeting:
- Governance and routing decisions for Matrix bot alerts (ai-ml/tickets#42)
- Participation in This Week in Fedora (TWIF) automated chat summarization (ai-ml/tickets#39)
- ROCm 10.1 status in preview Copr and upcoming sidetag rebuild
- Scoping introductory AI/ML user guides and tooling tutorials (ai-ml/tickets#6)
- Fedora Wiki to Fedora Docs documentation content plan and workflow transition (ai-ml/tickets#40)
Note: LLM-gen-AI was used to summarize the Meetbot-generated HTML log of the public meeting. I edited the AI-generated output before making this Fedora Discussion topic. If you notice mistakes, please provide a correction as a reply to this topic.
Links to Meeting Logs
Executive Summary
The meeting began with two swift administrative decisions regarding Matrix communication channels. First, to eliminate channel clutter while preserving diagnostic visibility, the SIG approved relocating automated notifications to a dedicated alerts room (ai-ml/tickets#42). Justin Wheeler (@jflory7) will update the Nonbot webhooks accordingly. Second, the group considered an opt-in request for Aurélien Bompard’s (@abompard) automated summarization bot for This Week in Fedora (TWIF) (ai-ml/tickets#39). Tim Flink (@tflink) voiced caution regarding LLM tendencies to state preliminary discussions with unwarranted certainty and the broader sensitivities surrounding AI-generated summaries. @jflory7 noted ongoing work with @abompard to publish these digests to the Community Blog, where community members can more easily flag inaccuracies as replies to Fedora Discussion topics. The SIG agreed to proceed with caution, with the explicit condition that it can be disabled if factual inaccuracies arise.
On the packaging front, Tom Rix (@trix) reported that ROCm 10.1 is now available in the preview Copr repository and compiling cleanly, including downstream consumers such as PyTorch. Initial ABI breakage testing is underway using pi-coding-agent. Barring unexpected blockers, packaging changes will be checked in over the weekend, with a multi-day Koji sidetag rebuild expected to commence early next week. The new stack introduces initial compiler support for the gfx1170 APU, updates the toolchain to LLVM 24, and incorporates preliminary support for Khronos SPIR-V standard GPU compilation.
Finally, the SIG held an extensive discussion on documentation strategy. The team first brainstormed potential getting-started guides (ai-ml/tickets#6), with Gordon Messmer (@gordonmessmer) suggesting documentation on installing pi-coding-agent with local models. Discussion then turned to ai-ml/tickets#40, where @jflory7 proposed migrating SIG documentation from the Fedora Wiki to Fedora Docs to leverage Antora, git pull requests, and dedicated Docs Team resources. Both @trix and @tflink expressed strong skepticism, emphasizing that changing documentation engines does not solve the fundamental constraint of finding contributors willing to keep technical documentation fresh. @trix reiterated that his focus remains strictly on packaging. With the meeting running up against a hard stop, the SIG agreed to continue the conversation asynchronously in the ticket.
Action Items
- @jflory7: Reconfigure Nonbot webhooks as documented in ticket #42
- @jflory7: Summarize this discussion into ticket #6, with an intent to revisit as documentation work gets further along. May or may not continue tracking user guide content work from that issue.
- @jflory7:
Post meeting summary to Fedora Discussion - @jflory7: Post updates on all tickets discussed in today’s meeting
Detailed Meeting Log
Topic: Rally for quick voting decisions on two tickets, discuss if needed
The meeting opened with @jflory7 reviewing two low-consequence procedural tickets pending consensus.
Ticket: ai-ml/tickets#42 (Dedicated Room for Bot Alerts)
@jflory7 proposed moving bot alerts out of the main AI/ML SIG Matrix discussion room into a dedicated, joinable room to keep chatter clean while retaining a public audit log. @tflink asked whether members find Matrix alerts helpful in practice; @jflory7 responded that alerts are valuable when kept in a separate channel that can be muted and checked on demand. @tflink supported the change as a +0, noting that he would advocate eliminating or isolating alerts if traffic increased. @trix noted he had already left feedback on the proposal. With no objections raised, the SIG reached consensus:
-
Agreed (verbatim): “For #42, the AI/ML SIG will remove bot alerts from the main Matrix room, and create a new room for bot alerts only. Anyone can join the alerts room if they desire. @jflory7 can carry this out as a member of the Matrix WG.”
-
Action: @jflory7 will reconfigure the Nonbot webhooks to complete the room transition.
Ticket: ai-ml/tickets#39 (Opt-in to TWIF Matrix Summarization Bot)
The discussion turned to whether the SIG should authorize @abompard’s automated bot to ingest the AI/ML SIG Matrix channel history to generate weekly summaries for This Week in Fedora (TWIF).
@tflink shared reservations about opting in, noting two main concerns: past instances where Meetbot automated summaries interpreted tentative discussions with excessive certainty, and the heightened community sensitivity surrounding AI-generated content. He cautioned that LLM inaccuracies might cause community members outside the SIG to become alarmed over tentative technical ideas. @jflory7 acknowledged these risks, noting that straightforward technical topics like ROCm packaging carry less risk than thorny philosophical discussions, but stressed that testing the tool is the best way to evaluate its utility. He added that he is collaborating with @abompard on WordPress integration for the Community Blog, ensuring summaries have associated Fedora Discussion threads where readers can correct mistakes.
@jflory7 suggested running a trial period without closing the ticket immediately. @tflink agreed that enabling ingestion with the understanding that it can be revoked at any time was acceptable. The team adopted the proposal:
- Agreed (verbatim): “The AI/ML SIG agrees to let @abompard’s summarization bot to ingest AI/ML SIG chat room history for weekly reports. This can be turned off later if the report accuracy is questionable. All SIG members are encouraged to read the weekly report and identify any inaccuracies worth correcting.”
Topic: ROCm 10.1 in preview copr
@trix briefed the team on the current packaging status of ROCm 10.1:
-
Build Status: ROCm 10.1 packages are available in the rocm-packagers-sig preview Copr. Everything has compiled cleanly, including large consumer packages like PyTorch.
-
Testing & Sidetags: ABI and functional validation is in progress using
pi-coding-agent. Pending test results, @trix intends to commit changes over the weekend, confirm Red Hat internal Copr build status, and initiate a Koji sidetag rebuild early next week. Because of long-polling packages in the stack, the sidetag build is projected to take 4 to 5 days. -
Info (verbatim): “ROCm 10.1 update has started in COPR and appears to be going well, sidetag rebuild will probably start next week if initial testing goes well”
-
Toolchain & Hardware Changes: The compiler stack has updated to LLVM 24. It introduces support for the
gfx1170APU, though actual hardware is not yet in user hands. Additionally, initial compiler support for Khronos SPIR-V has landed. @tflink noted that Khronos SPIR-V standardizes intermediate shader/kernel representations across GPU vendors, and @trix noted that its JIT-based architecture will present both advantages and challenges as upstream adoption develops.
Ticket: ai-ml/tickets#6 (Examples of Getting Started with AI on Fedora Linux)
@jflory7 brought up ticket #6 to assess whether the SIG should continue tracking beginner onboarding documentation under this older ticket or begin fresh within the newer documentation site. @tflink remarked that the ticket was an older one-sentence stub and supported closing or replacing it with specific tasks.
@trix emphasized that documentation progress hinges entirely on having dedicated technical writers, noting that his capacity is focused on RPM packaging. @jflory7 clarified that he has allocated time through Red Hat and his co-lead role on the Fedora Docs Team to contribute documentation.
The group brainstormed content ideas for Fedora AI user guides:
-
@gordonmessmer suggested writing a guide on installing
pi-coding-agentand running it with local models. -
@tflink asked about the target audience, suggesting that graphical tools like a packaged
lemonade-servermight appeal to users seeking non-terminal workflows. -
@jflory7 recorded current user guide ideas into the record: local inference setups (Ollama, llama.cpp, RamaLama), GPU tuning (AMD, Intel, Nvidia), model execution, coding agents (
pi-coding-agent, OpenClaw, Claude Code), and generative media applications.
@jflory7 took an action item to record this feedback in ticket #6 and evaluate whether to keep tracking beginner guide efforts there or split them into targeted tickets.
Ticket: ai-ml/tickets#40 (Wiki & Fedora Docs Content Plan)
@jflory7 introduced his proposal to migrate the AI/ML SIG documentation from the Fedora Wiki to Fedora Docs (Antora). He explained that a modern git repository workflow on Forgejo allows for granular page stewardship via CODEOWNERS, aligns the SIG with standard Fedora documentation infrastructure, and benefits from dedicated Fedora Docs team writers and sysadmins. He added that wiki pages are deprioritized in search engine ranking and lack active maintenance communities.
The proposal met with strong pushback:
-
@tflink and @trix debated that changing the publishing platform does not resolve the root problem: a lack of contributors dedicated to maintaining and updating technical information over time.
-
@trix expressed a firm objection (“hard no”), clarifying that he has zero interest in joining the Fedora Docs team or managing documentation migrations, and reiterated that his commitment to the SIG is strictly packaging.
-
@jflory7 explained that he was offering to do the writing and migration work himself, breaking migrations into small, non-disruptive pull requests, while allowing maintainers to commit directly to
mainfor quick fixes. -
@tflink agreed with avoiding heavy review processes for routine changes, noting the SIG is too small for excessive procedural overhead, but remained unconvinced that moving away from the wiki would fix content rot.
With the meeting reaching its scheduled conclusion at 17:30 UTC, @tflink recorded an informational note that time had expired and the discussion would continue asynchronously in the Forgejo ticket.