Create a Welcoming First-Page Navigation Experience #29
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
No due date set.
Dependencies
No dependencies set.
Reference
ai-ml/tickets#29
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
We need to have a single place to point new contributors to get started.
Background
Over the years (wow, it's been that long?) I've had people emailing me directly about the SIG. I'm happy to welcome new contributors, but I need a great place to send them! :)
In the past I'd link them to https://fedoraproject.org/wiki/SIGs/AI-ML#Get_Involved and ask them to join us on Matrix. It was a small group and we'd usually have someone in the channel to welcome them further.
The wiki page is a little stale, and we have https://docs.fedoraproject.org/en-US/ai/ which is not helpful.
A place were we can funnel contributors, end-users, and all interested parties to would be lovely.
Details
Have one place, have it well known, update links across our ecosystem, evolve from there.
I suspect we need a few tracks from the same landing spot:
packagersthat would like to help with the SIG packages (i.e. group membership for the packaging groups)Outcome
A clear landing spot for navigating the SIG/WG
There's also some info on the forge profile - https://forge.fedoraproject.org/ai-ml
Makes sense to consolidate to one place and link other pages to it so there's no need to keep multiple sources up to date.
Building on this, here are some specific ideas for what the page should cover:
The FAS group membership question (separating community participation from infrastructure access) is being tracked separately in #34.
Assisted-by: Claude Opus 4.6 (1M context)
Fixed by ai-ml/docs#1.