2023-12-07 14:02:41 <@tflink:fedora.im> !startmeeting PyTorch
2023-12-07 14:02:41 <@meetbot:fedora.im> Meeting started at 2023-12-07 14:02:41 UTC
2023-12-07 14:02:41 <@meetbot:fedora.im> The Meeting name is 'PyTorch'
2023-12-07 14:02:54 <@tflink:fedora.im> !topic welcome
2023-12-07 14:03:16 <@tflink:fedora.im> !chair Kaitlyn
2023-12-07 14:03:37 <@tflink:fedora.im> sorry, this is the first time I've tried to use the new meetbot
2023-12-07 14:04:17 <@tflink:fedora.im> !halp
2023-12-07 14:04:25 <@tflink:fedora.im> !undo
2023-12-07 14:04:26 <@kaitlynabdo:fedora.im> no worries, ive never used it either so thanks!
2023-12-07 14:04:56 <@tflink:fedora.im> sorry to whoever ends up reading these logs, they might be a bit messy :)
2023-12-07 14:05:06 <@tflink:fedora.im> !hello
2023-12-07 14:05:08 <@zodbot:fedora.im> Tim Flink (tflink)
2023-12-07 14:05:16 <@kaitlynabdo:fedora.im> so the two things i have on the agenda for today is just general updates and then talk about a change proposal
2023-12-07 14:05:38 <@tflink:fedora.im> is it just the three of us?
2023-12-07 14:06:06 <@kaitlynabdo:fedora.im> i think so
2023-12-07 14:07:05 <@trix:fedora.im> everyone is _using_ the shiny new pytorch :)
2023-12-07 14:07:52 <@tflink:fedora.im> I guess we can get started, then
2023-12-07 14:07:57 <@tflink:fedora.im> !topic General Updates
2023-12-07 14:08:09 <@trix:fedora.im> which is my update.. pytorch is in rawhide
2023-12-07 14:08:20 <@tflink:fedora.im> \o/
2023-12-07 14:08:22 <@kaitlynabdo:fedora.im> OMG thats great!!!
2023-12-07 14:08:54 <@mystro256:fedora.im> 👍️
2023-12-07 14:09:10 <@mystro256:fedora.im> 🎊
2023-12-07 14:09:36 <@mystro256:fedora.im> oh look at that, element show confeti
2023-12-07 14:10:05 <@kaitlynabdo:fedora.im> so ive never submitted a change proposal before, has anyone here done that?
2023-12-07 14:10:28 <@tflink:fedora.im> I assume that's all the updates, then?
2023-12-07 14:10:39 <@trix:fedora.im> more updates...
2023-12-07 14:11:03 <@trix:fedora.im> most of ROCm math is in,  ROCm AI is current todo list
2023-12-07 14:11:56 <@trix:fedora.im> I am workingon the pytorch examples.. lots of things to do there,  i have torchtext,data,viedo queued up for review
2023-12-07 14:12:36 <@tflink:fedora.im> !info pytorch is now in rawhide
2023-12-07 14:12:52 <@tflink:fedora.im> !info most of ROCm math has been packaged
2023-12-07 14:13:31 <@trix:fedora.im> i am reviewing openvino, it has issue with large third_party like pytorch
2023-12-07 14:13:52 <@tflink:fedora.im> !info more packages are pending, torch text, data and video
2023-12-07 14:14:25 <@tflink:fedora.im> yeah, that does seem to be a common thing to do nowadays. is it like pytorch where it's all git subrepos?
2023-12-07 14:15:42 <@trix:fedora.im> yeah. so there is stuff to unwind in openvino.
2023-12-07 14:16:19 <@tflink:fedora.im> oof, I was hoping you were going to say no but kinda knew better
2023-12-07 14:17:55 <@trix:fedora.im> if we could find the intersection of openvino needs and pytorch packages we could still use, i think we could move both along.
2023-12-07 14:18:24 <@trix:fedora.im> some things like mkl depend on dpc++ and i don't think we have that compiler in fedora
2023-12-07 14:18:48 <@tflink:fedora.im> are there still pytorch deps left to package? obviously not the critical ones but any for additional functionality that isn't currently enabled?
2023-12-07 14:19:24 <@trix:fedora.im> yes. still functionality to do.. we just have a minimal thing going
2023-12-07 14:19:43 <@trix:fedora.im> folks are asking about opencl support
2023-12-07 14:20:28 <@trix:fedora.im> lots of hw we could plug in.  just my focus is on rocm. so looking for who wants to handle others
2023-12-07 14:22:44 <@tflink:fedora.im> !info there are still pytorch deps left to do for additional functionality
2023-12-07 14:22:48 <@tflink:fedora.im> !link https://fedoraproject.org/wiki/SIGs/PyTorch/packagingStatus
2023-12-07 14:23:00 <@tflink:fedora.im> anything else before we move on?
2023-12-07 14:23:15 <@trix:fedora.im> nope.. i'm typed out!
2023-12-07 14:24:04 <@tflink:fedora.im> thanks for the updates!
2023-12-07 14:24:25 <@tflink:fedora.im> !topic Change Proposal
2023-12-07 14:26:52 <@kaitlynabdo:fedora.im> is this release of pytorch ready so that we can submit a change proposal?
2023-12-07 14:27:44 <@trix:fedora.im> what is needed for 'ready' ?
2023-12-07 14:27:59 <@trix:fedora.im> i do not know what a change proposal is 
2023-12-07 14:28:52 <@kaitlynabdo:fedora.im> if its something that will be part of the next fedora release
2023-12-07 14:29:22 <@trix:fedora.im> its in rawhide, doesn't it just roll into the next release automatically ?
2023-12-07 14:29:49 <@tflink:fedora.im> yeah, it'd be more of an advertising thing. not sure if a change proposal is strictly required for pytorch
2023-12-07 14:30:03 <@kaitlynabdo:fedora.im> the change proposal is just some paperwork that is supposed explain what youre putting into it
2023-12-07 14:30:09 <@kaitlynabdo:fedora.im> ^^ yes exactly
2023-12-07 14:30:45 <@kaitlynabdo:fedora.im> the change proposal is just some paperwork that is supposed explain what youre putting into it and why
2023-12-07 14:30:47 <@trix:fedora.im> ok lets work on the paperwork.. maybe i can get a tour of pacific islands out of it !?!?
2023-12-07 14:30:58 <@tflink:fedora.im> when are the F40 change proposals due?
2023-12-07 14:31:13 <@kaitlynabdo:fedora.im> https://fedorapeople.org/groups/schedule/f-40/f-40-key-tasks.html
2023-12-07 14:31:34 <@tflink:fedora.im> 2024-01-26 is what it looks like
2023-12-07 14:31:38 <@kaitlynabdo:fedora.im> 1/16/24 since this is a self contained change
2023-12-07 14:31:45 <@kaitlynabdo:fedora.im> so weve got some time
2023-12-07 14:32:29 <@kaitlynabdo:fedora.im> what ill do is start putting together stuff and then ill share it w everyone
2023-12-07 14:32:29 <@tflink:fedora.im> with a 2024-02-06 branch date if there are more packages/functionality we wanted to get into F40
2023-12-07 14:32:36 <@trix:fedora.im> nice! a schedule.. i am clueless you can see
2023-12-07 14:32:59 <@trix:fedora.im> if you want to poke me offline, i can help out 
2023-12-07 14:34:14 <@tflink:fedora.im> !info 2024-01-26 is the F40 due date for self-contained changes
2023-12-07 14:35:14 <@tflink:fedora.im> !action Kaitlyn to start putting a F40 change proposal draft for pytorch
2023-12-07 14:36:31 <@kaitlynabdo:fedora.im> ya next steps then are to start putting together the change proposal and also like tim said focus on if theres any more packages/functionality to add that will be included in the change
2023-12-07 14:37:21 <@mystro256:fedora.im> Are we starting to actually put pytorch and rocm as a part of fedora change proposals now?
2023-12-07 14:37:41 <@mystro256:fedora.im> I.e. should I start worrying about planning what ROCm release goes into what Fedora release?
2023-12-07 14:38:12 <@tflink:fedora.im> I'm not sure that we need to be doing change proposals for every release
2023-12-07 14:38:16 <@mystro256:fedora.im> I'm sort of doing it adhoc right now
2023-12-07 14:38:30 <@trix:fedora.im> 6 is coming up.. and we have about 4 ai ones yet to do
2023-12-07 14:38:49 <@trix:fedora.im> could we pause on 6 to to get the ai ones in ?
2023-12-07 14:39:04 <@mystro256:fedora.im> 6 as in ROCm 6.0?
2023-12-07 14:39:07 <@trix:fedora.im> yes
2023-12-07 14:39:30 <@tflink:fedora.im> is there a huge difference in packaging the remaining bits for 5.7 vs 6?
2023-12-07 14:39:36 <@mystro256:fedora.im> I'd like to get 6.0 into F40 if we have the runway for it
2023-12-07 14:39:50 <@mystro256:fedora.im> I think there's some breaking changes, but I need to review the changes
2023-12-07 14:39:51 <@tflink:fedora.im> is the release date for 6.0 public?
2023-12-07 14:40:11 <@trix:fedora.im> folks are asking for 6 now.. 
2023-12-07 14:40:24 <@mystro256:fedora.im> not sure, but it's soon™
2023-12-07 14:40:40 <@mystro256:fedora.im> yeah and if I don't get it into f40, I'll need to wait till 41, since it's breaking
2023-12-07 14:40:44 <@tflink:fedora.im> it looks like 6.0 was announced yesterday?
2023-12-07 14:40:52 <@mystro256:fedora.im> backporting 5.7 wasn't that bad for f39 in comparison
2023-12-07 14:41:00 <@mystro256:fedora.im> hold on, let me check
2023-12-07 14:41:23 <@tflink:fedora.im> https://www.phoronix.com/review/amd-instinct-mi300-rocm6/2
2023-12-07 14:41:58 <@tflink:fedora.im> it doesn't give a date, just that 6.0 is coming
2023-12-07 14:42:32 <@trix:fedora.im> can we do both ?
2023-12-07 14:42:41 <@mystro256:fedora.im> both what?
2023-12-07 14:42:57 <@tflink:fedora.im> 6.0 at the same time we get the last ai-related packaged reviewed?
2023-12-07 14:43:03 <@trix:fedora.im> rocm 6 and the 4 or so remaining ai packages to get rocm+pytorch going
2023-12-07 14:43:27 <@mystro256:fedora.im> sure, I can put the ai/ml when I'm updating to 6.0, and we can see if there's any buzz
2023-12-07 14:43:39 <@mystro256:fedora.im> sure, I can poke the ai/ml when I'm updating to 6.0, and we can see if there's any buzz
2023-12-07 14:43:59 <@tflink:fedora.im> are those remaining packages needed for rocm support in pytorch? I assume so
2023-12-07 14:44:34 <@trix:fedora.im> yes, generally we need MIOpen and it has some dependencies not currently track on the HC page
2023-12-07 14:44:51 <@mystro256:fedora.im> is there anything in 6.0 you're waiting for?
2023-12-07 14:45:02 <@mystro256:fedora.im> I know there's some issues blocking debian, but I haven't reviewed it
2023-12-07 14:45:27 <@trix:fedora.im> if i _had_ an mi300 to play with, yes.. but i don't so 5.7 is ok 
2023-12-07 14:46:01 <@mystro256:fedora.im> ok, well I'll monitor the rocm announcements and start a sidetag when I'm starting the upgrade
2023-12-07 14:46:30 <@mystro256:fedora.im> Point being, F40 should have 6.0 in it, so we'll try to make it as smooth as possible
2023-12-07 14:46:48 <@trix:fedora.im> ok. we do that
2023-12-07 14:47:03 <@tflink:fedora.im> sounds good
2023-12-07 14:47:24 <@mystro256:fedora.im> someone will have to take over when 6.1 comes out because I'll be on parental leave
2023-12-07 14:47:40 <@tflink:fedora.im> whether we want to do a F40 change proposal for rocm is probably a question for another time
2023-12-07 14:48:15 <@tflink:fedora.im> Jeremy Newton congratulations, we'll make sure that someone is doing that work
2023-12-07 14:48:24 <@mystro256:fedora.im> thanks!
2023-12-07 14:48:49 <@trix:fedora.im> yes.. the awesome rocm-packagers sig!
2023-12-07 14:49:02 <@tflink:fedora.im> :)
2023-12-07 14:49:15 <@trix:fedora.im> we will keep stuff going
2023-12-07 14:49:18 <@tflink:fedora.im> anyhow, we seem to have drifted topic a bit
2023-12-07 14:49:28 <@tflink:fedora.im> anything else on the F40 change proposal for pytorch?
2023-12-07 14:49:58 <@trix:fedora.im> just get the doc started and we can help out
2023-12-07 14:50:16 <@kaitlynabdo:fedora.im> yep thats it from me
2023-12-07 14:50:26 <@tflink:fedora.im> ok, moving on to ...
2023-12-07 14:50:29 <@tflink:fedora.im> !topic open floor
2023-12-07 14:50:38 <@tflink:fedora.im> any other topics that folks want to bring up?
2023-12-07 14:51:06 <@tflink:fedora.im> just to summaraize some things from before
2023-12-07 14:51:16 <@tflink:fedora.im> !info rocm 6.0 is expected for F40
2023-12-07 14:51:27 <@tflink:fedora.im> !info a few deps are remaining to get rocm support into pytorch
2023-12-07 14:52:02 <@tflink:fedora.im> anything else or shall we set the timer and adjourn?
2023-12-07 14:52:24 <@tflink:fedora.im> next meeting will be google, right?
2023-12-07 14:52:43 <@tflink:fedora.im> are we doing it on the 21st or will it be after the first of the year?
2023-12-07 14:52:57 <@kaitlynabdo:fedora.im> its going to be after the first of the year and yes it will be google
2023-12-07 14:53:28 <@kaitlynabdo:fedora.im> ill send out emails and post something on fedora discussion when the next meeting happens in the new year so some more ppl might join
2023-12-07 14:53:30 <@tflink:fedora.im> January 4th, then?
2023-12-07 14:53:42 <@kaitlynabdo:fedora.im> yes!
2023-12-07 14:53:59 <@tflink:fedora.im> !info no pytorch meeting in 2 weeks
2023-12-07 14:54:11 <@tflink:fedora.im> !info next pytorch meeting will be on January 4, 2024
2023-12-07 14:54:18 <@tflink:fedora.im> !undo
2023-12-07 14:54:32 <@tflink:fedora.im> !info next pytorch meeting will be via google meeting on January 4, 2024
2023-12-07 14:54:48 <@tflink:fedora.im> I guess I'll find out if !undo works when I look at the meeting logs :)
2023-12-07 14:55:02 <@tflink:fedora.im> anyhow, it sounds like that's it for today
2023-12-07 14:55:21 <@tflink:fedora.im> unless there are more bits to discuss, will end the meeting in a minute or so
2023-12-07 14:55:37 <@kaitlynabdo:fedora.im> yep i think so, how do we get meeting notes from meetbot
2023-12-07 14:56:05 <@tflink:fedora.im> the link will show up here after I end the meeting, at least
2023-12-07 14:56:22 <@kaitlynabdo:fedora.im> oohh okay sounds good
2023-12-07 14:56:38 <@tflink:fedora.im> not sure if the integration with meetbot.fp.o is working yet
2023-12-07 14:57:01 <@tflink:fedora.im> Thanks for coming, everyone
2023-12-07 14:57:05 <@tflink:fedora.im> !endmeeting