<@tflink:fedora.im>
16:30:34
!startmeeting fedora-ai-ml-sig
<@meetbot:fedora.im>
16:30:35
Meeting started at 2026-08-27 16:30:34 UTC
<@meetbot:fedora.im>
16:30:35
The Meeting name is 'fedora-ai-ml-sig'
<@trix:fedora.im>
16:31:28
!hi
<@zodbot:fedora.im>
16:31:29
Tom Rix: Tom Rix (trix)
<@cybette:matrix.org>
16:31:58
!hi
<@tflink:fedora.im>
16:32:01
!hi
<@zodbot:fedora.im>
16:32:01
Carol Chen: Carol Chen (cybette) - she / her / hers
<@zodbot:fedora.im>
16:32:03
tflink: Tim Flink (tflink)
<@man2dev:fedora.im>
16:32:44
!hi
<@zodbot:fedora.im>
16:32:46
Mohammadreza Hendiani: Mohammadreza Hendiani (man2dev)
<@tflink:fedora.im>
16:34:21
ok, let's get this party started
<@thunderbirdtr:fedora.im>
16:34:27
!hi
<@zodbot:fedora.im>
16:34:29
Onuralp S.: Onuralp SEZER (thunderbirdtr) - he / him / his
<@tflink:fedora.im>
16:34:31
!topic pytorch 2.13
<@tflink:fedora.im>
16:35:43
Tom Rix: this one is yours
<@trix:fedora.im>
16:36:42
working on the 2.13 has stalled because of libstdc++ update conflicting with rocm , breaking this and rocfft.
<@tflink:fedora.im>
16:36:52
in f45 and rawhide, yes?
<@trix:fedora.im>
16:37:06
yes that happened today in f45
<@trix:fedora.im>
16:37:19
see my ranting on ai/ml channel.
<@tflink:fedora.im>
16:37:24
!info work on pytorch 2.13 has stalled due to new problems with rocm in rawhide and f45 due to libstdc++ update
<@tflink:fedora.im>
16:37:57
is there more to talk about or shall we move on?
<@trix:fedora.im>
16:38:33
we can move on, as the tides comes, so do last minute toolchain updates come to fedora releases.
<@tflink:fedora.im>
16:39:19
!topic ROCm 10.0 planning
<@trix:fedora.im>
16:39:23
next bit is ROCm 10 has landed in the public.
<@trix:fedora.im>
16:39:52
this may or may not be a big deal, i am treating it as a big deal until i know otherwise.
<@tflink:fedora.im>
16:40:07
!info ROCm 10.0 was released on 2026-08-26, this is a major upgrade and marks a shift in ROCm's release pace going forward
<@trix:fedora.im>
16:40:27
https://fedoraproject.org/wiki/Changes/ROCm_8.x
<@man2dev:fedora.im>
16:40:28
Is there huge change?
<@tflink:fedora.im>
16:40:41
for some reason, they changed rocm 8 to rocm 10
<@trix:fedora.im>
16:40:49
should be renamed to 10. crazy amd guys with their naming :)
<@tflink:fedora.im>
16:40:51
so whatever was said about rocm 8 in the past is now rocm 10
<@trix:fedora.im>
16:40:56
yes.
<@man2dev:fedora.im>
16:41:25
The only news I heard about it was that some new target gpu got added.
<@tflink:fedora.im>
16:42:23
from an ABI POV, I don't think there is a huge change when compared to 7.2. there shouldn't be much change from 7.14. the biggest changes are release cadence and support model AFAIK
<@trix:fedora.im>
16:42:24
it may just be maketing, but major version changes are a license to make breaking abi changes. we need to manage abi breakage
<@tflink:fedora.im>
16:42:58
note the "should" in what I said. we haven't confirmed the size of changes yet
<@trix:fedora.im>
16:43:23
that's what i will be doing asap. 10 is going into this copr
<@tflink:fedora.im>
16:43:40
the fact that libabigail seems to be crashing on the 7.14 debuginfo packages isn't helping that check go any faster :-/
<@trix:fedora.im>
16:43:44
https://copr.fedorainfracloud.org/coprs/g/rocm-packagers-sig/preview/packages/
<@tflink:fedora.im>
16:44:00
!link https://copr.fedorainfracloud.org/coprs/g/rocm-packagers-sig/preview/packages/
<@trix:fedora.im>
16:44:00
yes libabigail is crashing on debug info.
<@tflink:fedora.im>
16:44:22
have you filed a bug against libabigail? I was about to
<@trix:fedora.im>
16:44:38
i was working around it.
<@tflink:fedora.im>
16:44:51
claude seems to think it's due to some change in DWARF in new GCC or LLVM
<@trix:fedora.im>
16:45:06
i did file a bug against fedora-review not working :(
<@tflink:fedora.im>
16:45:25
anyhow, I'm bringing the meeting into a rathole. we can continue that conversation offline
<@trix:fedora.im>
16:45:29
https://fedoraproject.org/wiki/SIGs/HC#Testing
<@tflink:fedora.im>
16:46:08
!info rocm 10.0 is being packaged and updated, will stay in @rocm-packagers-sig/preview COPR until some basic testing has been done and the scope of changes has been better quantified
<@trix:fedora.im>
16:46:19
has the 'pkgdiff' tests. i used those on 7.14, so we have got that covered, if not completely documented.
<@trix:fedora.im>
16:47:21
it will be a matter of using them once 10 is in the copr. it will compare that copr package to rawhide package.
<@trix:fedora.im>
16:48:41
i sorta kitchen sinked the pkgdiff test. if there is some other pkg tests i missed, send me a pr and i'll get the changes into the set of dockers. the sooner the better.
<@tflink:fedora.im>
16:49:36
ok, I'll follow up with you offline about making progress there. I just started poking at abi checks for rocm packages the other day
<@trix:fedora.im>
16:49:47
cool.
<@tflink:fedora.im>
16:50:04
anything else on this?
<@trix:fedora.im>
16:50:13
maybe we can sic some ai on the analysis
<@tflink:fedora.im>
16:50:16
other than the new need to re-name that rocm8 feature to rocm10?
<@trix:fedora.im>
16:50:34
yeah.
<@tflink:fedora.im>
16:50:57
but that won't be until F46 so we have a bit of time
<@trix:fedora.im>
16:51:28
yes. and we have the compat set already in place if things go badly.
<@tflink:fedora.im>
16:52:13
cool, any other topics for today? i have one short one that can wait until the end
<@trix:fedora.im>
16:52:28
all i got, thanks
<@tflink:fedora.im>
16:53:12
ok, I'll do my quick topic, then
<@tflink:fedora.im>
16:53:35
!topic ticket and PR feedback
<@tflink:fedora.im>
16:53:45
this is a quick one and mainly a "my bad" kind of thing
<@tflink:fedora.im>
16:54:05
I didn't realize how many open PRs were out there and some tickets waiting for feedback
<@tflink:fedora.im>
16:54:27
apologies for the delays there
<@tflink:fedora.im>
16:55:10
that's all, feel free to participate on those tickets/PRs if you'd like it wasn't a "tflink is the only one who can comment" kind of thing
<@tflink:fedora.im>
16:55:21
that's all, feel free to participate on those tickets/PRs if you'd like. it wasn't a "tflink is the only one who can comment" kind of thing
<@tflink:fedora.im>
16:55:41
with that, we can move on to ...
<@tflink:fedora.im>
16:55:43
!topic open floor
<@tflink:fedora.im>
16:55:51
any other items to discuss today?
<@man2dev:fedora.im>
16:56:19
Has anybody looked ito the licensing of Nemotron 3 family of models, evidently the new NVIDIA models are completely end-to-end open source. I'm not talking about just the weights on the model, I'm talking about even the data set or how to reproduce it. So theoretically it can be remade or it can be shipped as well, but I still haven't had the chance to look into all the licensing to confirm it, and make sure it's actually open source, but at least at least from the outside, it looks like Apache 2.
<@tflink:fedora.im>
16:57:01
I have not
<@man2dev:fedora.im>
16:57:50
If true, theoretically this could be the first model that we could ship as a package in Fedora.
<@man2dev:fedora.im>
16:58:18
Which I expect would be very interesting to see how rpm would react to
<@tflink:fedora.im>
16:58:39
AMD released a more open model a while back, it had training data and everything needed to build from scratch IIRC but it's been a while. The biggest problem I ran into was that the required HW to train it from scratch was very much non-trivial. I suspect that any open model might run into the same HW requirement problems
<@tflink:fedora.im>
16:59:19
I don't think that any part of Fedora has addressed the question of whether shipped models would have to be trained in-house and whether that could be done outside of koji
<@thunderbirdtr:fedora.im>
16:59:45
Mohammadreza Hendiani: sorry if it is stupid question if license okay, shipping how exactly ?
<@man2dev:fedora.im>
17:00:07
Yeah, the prices are insane. The closest thing that I can think of that might be able to build it and is the cheapest option, is the Mac Mini, I guess.
<@tflink:fedora.im>
17:00:28
the HW requirements for the AMD model was something along the lines of 8x MI210 at the low end, IIRC
<@tflink:fedora.im>
17:01:39
I think the question comes down to shipping binaries and whether open weights are acceptable. I don't think that any distro has really looked at shipping open weights yet but I could be wrong
<@tflink:fedora.im>
17:01:48
unless I'm misunderstanding your question
<@man2dev:fedora.im>
17:02:19
Well, theoretically, we would have to put it in RPM, or we could just make a DNF extension to call hugging face package clint but then we would need to have a hooking face compatible interface running on Fedora
<@trix:fedora.im>
17:02:52
for training models, my opinion is models should be trained in house, so we don't get stuck with a blob that may or may not work release to release.
<@thunderbirdtr:fedora.im>
17:03:45
My 2 cents opinion would be I wouldn't ? Most people use quantized and choose smarter via cli or tool better also agreed with Tom not every model work out of box. Support takes time or deals needs to be made so ship in day zero
<@thunderbirdtr:fedora.im>
17:04:08
But thank you for answering
<@man2dev:fedora.im>
17:04:53
No, you got my question correct. I don't want to, ship something that hasn't been reviewed and remade by us also, but I don't see us having the infrastructure for it unless some company sponsors us to do it
<@trix:fedora.im>
17:04:56
may need to up the 2 day timeout on koji 😅
<@thunderbirdtr:fedora.im>
17:05:19
I would say more than 2days. :)
<@tflink:fedora.im>
17:05:35
yeah, there is a real question about whether it would be worth it and whether it would be approved. anything built and shipped like that would probably not be at the top of any leader boards and would be difficult to update
<@tflink:fedora.im>
17:05:52
I don't think that there is any realistic way to have koji train models from scratch
<@thunderbirdtr:fedora.im>
17:06:41
A way of provide I would say (example install nvidia driver just meta package but download or tools that download blob/data but core package is there)
<@thunderbirdtr:fedora.im>
17:06:58
Also train %100 nope
<@tflink:fedora.im>
17:06:59
I'm not saying that it couldn't be done, I just don't think that the kind of surgery/grafting into koji that would be required to have the HW needed to train models isn't realistic
<@man2dev:fedora.im>
17:07:01
I think the real value proposition comes after you build it once, because then fine-tuning it, to my understanding, is not that expensive as rebuilding it.
<@cybette:matrix.org>
17:07:48
I've heard of Nemotron but haven't looked into how "open" it is. The license is this: https://www.nvidia.com/en-us/agreements/enterprise-software/nvidia-nemotron-open-model-license/ which is not a recognized open source license like Apache (which I believe the AMD models were released under)
<@man2dev:fedora.im>
17:08:48
That's why I want to know, can we get access and use external hardware for such thing as packaging or in this case, I guess, model creation? The only other external hardware that we have access to, to my knowledge, is the AWS servers.
<@tflink:fedora.im>
17:09:42
if there is interest from Fedora as a whole, we could start looking into this but there are a lot of questions that would need to be addressed and proposals that would have to happen
<@tflink:fedora.im>
17:10:16
and we'd have to find a sponsor with deep pockets to get access to the HW needed to create some kind of "fedora model"
<@tflink:fedora.im>
17:10:47
which would almost definitely be borrowed stuff in the cloud
<@thunderbirdtr:fedora.im>
17:10:57
tflink: well I would ask/say we need datasets first (if not ready )
<@tflink:fedora.im>
17:11:23
lemme look for the AMD released model I looked at a while back. I think that included datasets and scripts to train
<@man2dev:fedora.im>
17:12:00
The dataset of nemotron 3 is on hogging face.
<@thunderbirdtr:fedora.im>
17:12:04
Side note I have 2dgx in house can do try depends on model but for tooling of course not gonna be under fedora system but I can offer help at least
<@tflink:fedora.im>
17:12:14
https://www.amd.com/en/developer/resources/technical-articles/introducing-amd-first-slm-135m-model-fuels-ai-advancements.html
<@tflink:fedora.im>
17:12:34
the link to sources etc. is at the bottom of the page
<@tflink:fedora.im>
17:13:23
there is a list of models here that may be a similar kind of open but I haven't looked into them in detail: https://www.amd.com/en/developer/resources/open-source-models.html
<@man2dev:fedora.im>
17:14:03
Just a quick look and I'm already finding a 404 page for one of the databases it uses.
<@tflink:fedora.im>
17:14:07
the newest model listed "was trained on 64x MI300 GPUs" yikes
<@thunderbirdtr:fedora.im>
17:15:10
I felt poor in my gpu :)
<@tflink:fedora.im>
17:15:11
there may be updated links, it's been a while and I doubt that the datasets disappeared entirely. it was released 2 years ago
<@man2dev:fedora.im>
17:15:14
Well, that's cool. I'll take a look at it.
<@tflink:fedora.im>
17:16:33
anything else on this or other topics for the remaining 15 minutes?
<@cybette:matrix.org>
17:17:24
Searching around for licenses, I just saw this: https://openmdw.ai/
<@cybette:matrix.org>
17:19:16
Looks like the latest Nemotron 3 Ultra is released under the openMDW (previous ones under Nvidia's nemotron license)
<@tflink:fedora.im>
17:20:19
I wondered if anything was using it yet but you already answered that question :)
<@tflink:fedora.im>
17:21:20
quite a few, apparently: https://huggingface.co/models?license=license:openmdw-1.1&sort=trending
<@cybette:matrix.org>
17:22:09
heh I just copied the same link
<@cybette:matrix.org>
17:22:10
yep
<@cybette:matrix.org>
17:23:00
anyway, just commenting, nothing much to contribute to the meeting otherwise 😆
<@tflink:fedora.im>
17:23:13
thanks for the input
<@tflink:fedora.im>
17:23:24
it seems like there are no other topics, so I'll close out the meeting
<@tflink:fedora.im>
17:23:28
thanks for coming, everyone
<@tflink:fedora.im>
17:23:36
!endmeeting