ai-ml/docs
12
1
Fork 0
Code Issues Pull requests 2 Activity Actions

📝 docs(index): Add vision and mission statement for AI/ML SIG #2

Open
jflory7 wants to merge 1 commit from add/vision-mission into main
pull from: add/vision-mission
merge into: ai-ml:main
Conversation 3 Commits 1 Files changed 2 +68 -25
jflory7 commented 2026-08-13 19:25:09 +00:00
Owner
Copy link

The index page was scaffolded from the Fedora Marketing team template and still referenced Ambassadors, social media, and marketing campaigns. Replace it with actual AI/ML SIG content: a vision statement positioning Fedora as the premier open source AI/ML platform, a mission listing the six areas of work the SIG performs, audience guidance, related SIG links, and communication/meeting references.

Also fix three incorrect attributes: the Discourse tag URL pointed to a page with the right tag but no set category, the Matrix channel was "#ai" instead of "#ai-ml", and the team summary was a placeholder.

Closes: ai-ml/tickets#27

A screenshot of the dark-mode "Fedora AI/ML SIG" documentation page on Fedora Docs. It details the group's vision, mission, target audience, related SIGs, communication channels, and meeting schedules using bulleted lists and body text.

The index page was scaffolded from the Fedora Marketing team template and still referenced Ambassadors, social media, and marketing campaigns. Replace it with actual AI/ML SIG content: a vision statement positioning Fedora as the premier open source AI/ML platform, a mission listing the six areas of work the SIG performs, audience guidance, related SIG links, and communication/meeting references. Also fix three incorrect attributes: the Discourse tag URL pointed to a page with the right tag but no set category, the Matrix channel was "#ai" instead of "#ai-ml", and the team summary was a placeholder. Closes: https://forge.fedoraproject.org/ai-ml/tickets/issues/27 ![A screenshot of the dark-mode "Fedora AI/ML SIG" documentation page on Fedora Docs. It details the group's vision, mission, target audience, related SIGs, communication channels, and meeting schedules using bulleted lists and body text.](/attachments/3ed09a4a-c5a7-4c77-9eae-9970558b1c9e "A screenshot of a dark-themed Fedora Docs web page titled \"Fedora AI/ML SIG,\" featuring sections with text and bulleted lists about the group's mission, communication, and meetings.")
image.png
716 KiB 
The index page was scaffolded from the Fedora Marketing team template
and still referenced Ambassadors, social media, and marketing campaigns.
Replace it with actual AI/ML SIG content: a vision statement positioning
Fedora as the premier open source AI/ML platform, a mission listing the
six areas of work the SIG performs, audience guidance, related SIG
links, and communication/meeting references.

Also fix three incorrect attributes: the Discourse tag URL pointed to a
page with the right tag but no set category, the Matrix channel was
"#ai" instead of "#ai-ml", and the team summary was a placeholder.

Closes: ai-ml/tickets#27

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
jflory7 force-pushed add/vision-mission from 9ac17c8423 to 18a2390fe9 2026-09-01 22:21:00 +00:00 Compare
trix commented 2026-09-04 14:56:18 +00:00
Owner
Copy link

A vision statement should talk to where we want to be, where ai will help get us to a brighter future. Something like..

The AI/ML SIG works toward a future where AI is free and open, where individuals have AI tools to develop within Fedora and for the whole open source community.

A vision statement should talk to where we want to be, where ai will help get us to a brighter future. Something like.. The AI/ML SIG works toward a future where AI is free and open, where individuals have AI tools to develop within Fedora and for the whole open source community.
👍 1
jflory7 commented 2026-09-04 15:55:01 +00:00
Author
Owner
Copy link

@trix Good point about emphasizing the impact we want to have in the wider AI space by pushing for more free and open tools and software. I think the vision statement I drafted covers most of that, but it focuses in on the operating system/Fedora specifically. We could broaden it more to capture a wider intent to push for a more open AI ecosystem generally.

@trix Good point about emphasizing the impact we want to have in the wider AI space by pushing for more free and open tools and software. I think the vision statement I drafted covers most of that, but it focuses in on the operating system/Fedora specifically. We could broaden it more to capture a wider intent to push for a more open AI ecosystem generally.
jflory7 commented 2026-09-04 16:38:40 +00:00
Author
Owner
Copy link

Echoing this comment from @tflink in Matrix into this PR review. My read on feedback from folks inside and outside of the SIG so far is that most of what is here makes sense, but the AI Developer Desktop remains a point of confusion. We should try and be as clear as possible about things before we merge this into the Fedora Docs site:

@gordonmessmer: what was the conclusion from those epic discourse threads about the AI developer desktop spin? I thought that it was shelved for the time being and you were going to work on the module stuff somewhat outside the fedora project umbrella. Did I misunderstand/mis-remember something?

Following recent discussion in #devel:fedoraproject.org, I have been thinking a lot about this part of the proposed charter specifically. I am wondering if it makes sense for us to run some of the project management aspects of the AI Developer Desktop / Project Resistor in the AI/ML SIG, and have some of the building blocks for that work live elsewhere, e.g. GitLab.com. There seems to be a strongly-held opinion that Fedora Remix work should not happen under our official Fedora Forge because it appears as an endorsement of that work, which could be problematic for the enablement of proprietary software and drivers.

I am aware that leaving room for the folks of this SIG to influence and weigh in on an AI Developer Desktop project is useful, but I also don't want people to feel we are bulldozing community feedback and our values. I personally feel that by letting a Fedora Remix work under this SIG's Forge org, we are not doing that. But the verdict does not seem to be in on that.

I don't know how to capture this AI Developer Desktop work in a way which allows members of this SIG to be involved and consulted, without shunting the work off to somewhere else completely remote like GitLab.

@gordonmessmer, clarity on your aims and objectives would be helpful here too.

Echoing this comment from @tflink in Matrix into this PR review. My read on feedback from folks inside and outside of the SIG so far is that most of what is here makes sense, but the AI Developer Desktop remains a point of confusion. We should try and be as clear as possible about things before we merge this into the Fedora Docs site: > @gordonmessmer: what was the conclusion from those epic discourse threads about the AI developer desktop spin? I thought that it was shelved for the time being and you were going to work on the module stuff somewhat outside the fedora project umbrella. Did I misunderstand/mis-remember something? Following recent discussion in `#devel:fedoraproject.org`, I have been thinking a lot about this part of the proposed charter specifically. I am wondering if it makes sense for us to run some of the project management aspects of the AI Developer Desktop / Project Resistor in the AI/ML SIG, and have some of the building blocks for that work live elsewhere, e.g. GitLab.com. There seems to be a strongly-held opinion that Fedora Remix work should not happen under our official Fedora Forge because it appears as an endorsement of that work, which could be problematic for the enablement of proprietary software and drivers. I am aware that leaving room for the folks of this SIG to influence and weigh in on an AI Developer Desktop project is useful, but I also don't want people to feel we are bulldozing community feedback and our values. I personally feel that by letting a Fedora Remix work under this SIG's Forge org, we are not doing that. But the verdict does not seem to be in on that. I don't know how to capture this AI Developer Desktop work in a way which allows members of this SIG to be involved and consulted, without shunting the work off to somewhere else completely remote like GitLab. @gordonmessmer, clarity on your aims and objectives would be helpful here too.
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin add/vision-mission:add/vision-mission
git switch add/vision-mission

Merge

Merge the changes and update on Forgejo.
git switch main
git merge --no-ff add/vision-mission
git switch add/vision-mission
git rebase main
git switch main
git merge --ff-only add/vision-mission
git switch add/vision-mission
git rebase main
git switch main
git merge --no-ff add/vision-mission
git switch main
git merge --squash add/vision-mission
git switch main
git merge --ff-only add/vision-mission
git switch main
git merge add/vision-mission
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
ai-ml/Members
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ai-ml/docs!2
No description provided.