Scope gpu01 access to ai-packagers-sig and open up ai-ml-sig membership #34
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
docs
type
packaging
type
skills
No milestone
No project
No assignees
3 participants
Notifications
Due date
Dependencies
No dependencies set.
Reference
ai-ml/tickets#34
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
Separate infrastructure access (specifically the
gpu01host) from general SIG membership by scoping it to theai-packagers-sigFAS group instead ofai-ml-sig.Background
Membership in the
ai-ml-sigFAS group currently grants access to shared infrastructure, including thegpu01host, which has attracted a lot of attention. That ties together two different things — community participation and hardware access. Anyone who wants to follow along with the SIG or contribute to documentation, skills, or governance shouldn’t need to be in a group that also grants hardware access.This proposal separates those concerns: keep
ai-ml-sigas the broad community group — open to anyone interested — and scope infrastructure access toai-packagers-sig, which is already focused on packaging and CI work.I’m putting this forward for SIG review and a vote. If the SIG approves, I’ll execute the changes below.
Details
gpu01host access toai-packagers-sigFAS group membership instead ofai-ml-sig.ai-ml-sigFAS group description to reflect that it is the community/discussion group — open to anyone interested in the SIG.ai-packagers-sigFAS group description to reflect that it manages access to packaging infrastructure and shared hardware.Outcome
SIG membership is clearly separated from infrastructure access, making it easier to welcome new contributors without conflating participation with hardware privileges.
Assisted-by: Claude Opus 4.6 (1M context)
Propose a newcomer guide for the AI/ML SIGto Scope gpu01 access to ai-packagers-sig and open up ai-ml-sig membershipI think it is too early to discuss the use.
@trix wrote in #34 (comment):
I agree. There are still too many things in progress to be able to make decisions around any of the GPU machines. I'm not saying that we can't do anything just that anything we figure out would be temporary, at best
Also, I want to make sure that infra is involved with any of these decisions. Are there any safeguards or checks in place to at least detect improper usage? It's not like there haven't been checkout-able systems managed by infra in the past but I don't remember much about them or how they were configured
Discussed in 2026-07-16 Fedora AI/ML SIG meeting.
@jflory7 flagged the significantly rewritten ticket for feedback. @tflink and @trix both said it is too early to formalize access decisions given the number of moving parts around hardware procurement and ownership. @gordonmessmer noted that an Acceptable Use Policy is needed regardless of access mechanism, since "CI" describes a mechanism, not a purpose. @tflink mentioned that Fedora Infrastructure has managed packager-checkout-able systems for exotic hardware in the past, so precedent exists.
wontfix, explaining that the GPU hardware is in a "transitionary/exploration" phase while we discover what acceptable use looks like for the Fedora community.Assisted-by: Claude Opus 4.6 (1M context)
@tflink wrote in #34 (comment):
When I open this new ticket soon for us to discuss it, I don't think there is any way we could be successful without working with Fedora Infrastructure on this. I'll make it clear beyond our own initial discussions and ideas that we need to put something together to present to Infrastructure.