Proposal: Evolve the AI/ML SIG into the Fedora AI Working Group (WG) #27
Labels
No labels
good first issue
help wanted
huge
needs
changes
needs
reporter feedback
needs
triage
quickfix
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
type
packaging
type
skills
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Depends on
Reference
ai-ml/tickets#27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Propose evolving the AI/ML SIG into the "Fedora AI Working Group" (Fedora AI WG) to encompass both our hardware enablement work and our future role in guiding open AI best practices.
Background
In recent meetings, we discussed how the current "AI/ML SIG" name might not fully capture the breadth of what this group does today and where we are heading tomorrow. While the roots are strongly planted in critical ML hardware enablement (like getting ROCm working on AMD GPUs), there is a growing need in the Fedora Project for a group to steward open, ethical AI practices and provide guidance for the broader community. The folks here have done the foundational work, giving this group a legitimate claim to step up into this broader leadership role. Evolving into a "Working Group" reflects this expanded scope and helps us build the critical mass needed to welcome new builders.
Details
docs.fedoraproject.org/aisite to reflect the unified identity.Outcome
There is a clear, forward-looking identity that welcomes new contributors and accurately reflects our dual mission of deep technical enablement and community stewardship.
As I mentioned in the previous (and my first) Fedora ai-ml-sig meeting, I have a preference for AI/ML. I first studied ML in college 25+ years ago 🧓 But I won't be too bothered if it's "Fedora AI", gotta roll with the times 🎢
I'm in full support of changing the name to whatever fits the group best.
One of the things I think we took into account when first starting this was combining a few nascent and/or small groups. We had originally thought there was going to be better/more alignment between HC, HPC and maybe Neuro groups.
We should have a group and access model that maps to what work is being completed in the SIG.
The thing I want to avoid is a branding exercise that is only for branding sake. The models of today have a direct genesis from traditional ML. Where should the more traditional ML contributors be attracted to? The hype machine tainted and overloaded "AI" branding. We should be sure to include all contributors that can help push this field forward and integrate the best ideas into Fedora.
Hi, I'm Chinni Sree, a newcomer here!
I just joined the community and this was actually one of the first discussions I came across. Honestly, "Fedora AI Working Group" sounds more open and inviting to me as someone new. When I was looking for a community to join, "AI Working Group" felt like a place where people are actively building things together, while "SIG" felt a bit more closed or technical.
But I do agree that we shouldn't lose the ML side of things a lot of what makes this group strong comes from that traditional ML foundation, and new people interested in ML should still feel this is the right place for them.
Just my two cents as someone who just walked through the door! Looking forward to contributing.
I'll more or less echo what @jsteffan said. When we set up the AI/ML SIG, we consolidated some existing groups and many of those groups had not been terribly active for a while. We made an active choice to make a larger tent for those groups because none of us had a desire to do more admin work and in practice, there weren't that many people involved at the time. I also remember the conclusion of "if this needs to change in the future because we have too many things to keep in a single group, we'll cross that bridge if/when we get there".
I don't have the spare cycles right now to be reworking anything but I'm not going to stop anyone else from doing it so long as it doesn't break any of our active stuff, especially the ROCm packaging SIG.
I'm one of the reasons why it's the AI/ML SIG instead of the AI SIG for pretty much the same reason @cybette mentioned - I remember working on this stuff before it was as cool and it was either machine learning or maybe deep learning if you were feeling trendy. I'm still not convinced it's actual AI but I'm also (sometimes) capable of recognizing when a fight is not worth the energy so I'll just go with whatever the group decides to do so long as I'm not the one doing all the renaming work :)