14:00:24 <pwhalen> #startmeeting Fedora IoT Working Group Meeting
14:00:24 <zodbot> Meeting started Wed Feb 19 14:00:24 2020 UTC.
14:00:24 <zodbot> This meeting is logged and archived in a public location.
14:00:24 <zodbot> The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:24 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:00:24 <zodbot> The meeting name has been set to 'fedora_iot_working_group_meeting'
14:00:24 <pwhalen> #chair pwhalen pbrobinson bcotton tdawson puiterwijk
14:00:24 <pwhalen> #topic roll call
14:00:24 <zodbot> Current chairs: bcotton pbrobinson puiterwijk pwhalen tdawson
14:00:34 <coremodule> .hello2
14:00:35 <pwhalen> good morning folks, who's here today?
14:00:36 <zodbot> coremodule: coremodule 'Geoffrey Marr' <gmarr@redhat.com>
14:00:37 <bcotton> .hello2
14:00:39 <zodbot> bcotton: bcotton 'Ben Cotton' <bcotton@redhat.com>
14:00:44 <tdawson> Howdy
14:01:00 <asamalik> tiny computers!! :D
14:01:48 * pwhalen gives it a couple of minutes for others to join
14:03:22 <pwhalen> pbrobinson is out today on pto, so I think we have the usual suspect for the most part
14:03:32 <pwhalen> lets gets started
14:03:41 <pwhalen> #topic 1) ==== Working Group process and admin  ====
14:03:41 <pwhalen> #link https://docs.fedoraproject.org/en-US/iot/
14:04:06 <pwhalen> I dont have anything for this, bcotton?
14:04:10 <pwhalen> or anyone else?
14:05:39 <pwhalen> #info Nothing new to report.
14:05:51 <pwhalen> #topic 2) ==== Fedora 31 status ====
14:05:51 <pwhalen> #info Latest compose available for testing
14:05:51 <pwhalen> #link https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-31-20200209.0/compose/
14:06:36 <pwhalen> in my limited testing this compose looked ok
14:07:05 <pwhalen> is anyone aware of any issues in F31?
14:07:38 * jsmith shows up late
14:07:49 <pwhalen> howdy jsmith
14:08:02 <jsmith> I'm not aware of anything new in F31 -- but I've been on the road for a couple of weeks
14:09:40 <pwhalen> #info No issues reported.
14:09:53 <pwhalen> #topic 3) ==== Fedora 32 status ====
14:09:54 <pwhalen> #info Latest compose available for testing
14:09:54 <pwhalen> #link https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-32-20200218.0/compose/
14:10:23 <pwhalen> I think the compose issues are now resolved in f32
14:11:06 <pwhalen> and we got a new compose today, so the latest is Fedora-IoT-33-20200219.0
14:11:44 <pwhalen> images look good on both arches, kickstart install seems ok as well.
14:11:56 <tdawson> I know it's still early, but do we have our IoT testing day set for f32?
14:12:11 <pwhalen> I am having an issue upgrading on the rpi3, need to look at it more
14:12:32 <pwhalen> tdawson, we do! I booked next week - Feb 26th
14:12:40 <pwhalen> that seems a little early now
14:13:02 <tdawson> Ya, earlier than I expected.
14:13:41 <pwhalen> Beta freeze is also next week, Tue 2020-02-25
14:14:02 <coremodule> I don't know if sumantro has sent out anything public about the test day to the list, only the calendar
14:14:05 <pwhalen> #info F32 Beta target - 2020-03-17
14:14:21 <tdawson> Oh, well if that is when beta freeze is, then that's a good time to test.
14:14:24 <coremodule> it could be changed if you feel it's necessary
14:14:25 <pwhalen> coremodule, right. so we could perhaps rebook it
14:14:45 <pwhalen> tdawson, it's coming quickly.
14:15:18 <pwhalen> And, we're a release blocking edition for F32, so maybe leaving it as next week is best to find things early
14:15:26 <tdawson> I haven't done any testing of the F32 images yet, so I don't know if it's ready or not.  I really just wanted/needed a deadline for getting my stuff setup.
14:16:15 <pwhalen> I think its looking better. However we have a large piece outstanding for deployment which is the initial-setup replacement.
14:16:56 <pwhalen> that might be the determining factor on *if* we can even do it next week
14:17:21 <pwhalen> sadly, I dont see puiterwijk here today for an update.
14:18:49 <jsmith> I'll be traveling on the 26th, so I won't be able to help with test day if we stick with that day.
14:20:02 <pwhalen> yea, I think its best we rebook at least a week to ensure we can test the images. perhaps even two weeks
14:20:16 <pwhalen> then we get jsmith too :)
14:20:23 <pwhalen> thoughts?
14:20:31 <jsmith> WORKSFORME
14:20:33 <coremodule> pwhalen, I can get that rolling with sumantro if that's the decision. It makes sense to me
14:20:51 <pwhalen> coremodule, that would be fantastic. Thanks!
14:21:03 <coremodule> move it exactly one week ahead?
14:21:04 <coremodule> sure!
14:21:55 <pwhalen> coremodule, yea. Maybe just book it on the calendar and I can check with folks to make sure we're ready and confirm at next weeks meeting. If we're a go then we email it out?
14:22:24 <coremodule> sounds good to me. I'll book it right now and wait for your email/message to announce it publicly
14:22:36 <pwhalen> thanks coremodule, much appreciated.
14:23:14 <coremodule> moving to march 4
14:23:16 <pwhalen> and if people can do some testing prior - installs should work fine and the disk images can be tested by copying your ssh key to the root home
14:23:31 <pwhalen> coremodule, perft, thanks
14:25:17 <pwhalen> #info IoT to be release blocking in Fedora 32.
14:25:28 <pwhalen> no pressure.
14:25:43 <coremodule> lol
14:25:47 <pwhalen> anything else to mention? concerns, etc?
14:26:27 <tdawson> Nothing from me, we addressed my concern/question
14:26:47 <coremodule> i have two things for the open floor
14:27:26 <pwhalen> #info Fedora 32 IoT test day booked for March 4th. Might need to be reevaluated next week.
14:28:25 <pwhalen> #topic 4) ==== Open Floor ====
14:28:36 <pwhalen> that's all I had, coremodule floor is yours :)
14:29:49 <coremodule> whoop! well, i spent some time with the qa team during/after devconf.cz and one of the main things we got from meeting in person was getting more qa presence in IoT now that it's blocking
14:30:08 <coremodule> so two things we'd like your perspectives on
14:31:05 <coremodule> a way to track IoT specific bugs in bugzilla; we were thinking an IoT bugzilla tracker bug, and everytime a bug is submitted, the submitter would use the tracker to mark the bug as IoT specific
14:31:43 <pwhalen> coremodule, that should already be set up.
14:31:48 <bcotton> not exactly
14:31:49 <coremodule> is there a way you guys currently track bugs that this would interfere with, or would this help organize bugzilla?
14:31:55 <bcotton> there's a bugzilla *component* for IoT
14:32:22 <bcotton> but i'm not sure why we'd flag bugs related to IoT in other components. we don't do that with any of the other editions
14:33:00 <bcotton> (the idea behind a component was that iot users coudl start there and we could reassign to other components (e.g. kernel, systemd, etc) as necessary)
14:35:23 <coremodule> bcotton, does that work for tracking the bugs? or would a tracker be useful and simpler?
14:36:28 <pwhalen> Tracker is here - https://bugzilla.redhat.com/show_bug.cgi?id=1269538
14:36:58 <coremodule> .bug 1269538
14:37:00 <zodbot> coremodule: 1269538 – (IoT) Tracker for IoT on Fedora - https://bugzilla.redhat.com/1269538
14:37:14 <coremodule> boom, so that answers that
14:37:14 <bcotton> oh hey, i didn't even know that existed :-)
14:37:31 <bcotton> which is a separate problem :-)
14:38:56 <pwhalen> coremodule, cool. what was the other thing?
14:38:58 <coremodule> the second thing; we'd like to make IoT easier to install for the end user. we talked about getting it into Fedora Media Writer and arm-image-installer. is this feasible? do you have any thoughts?
14:39:34 <pwhalen> coremodule, works with the installer and I dont see why it wouldnt work with the media writer
14:40:07 <pwhalen> for some aarch64 boards we need to write uboot to an offset, but the Raspberry Pi is all set up and ready to go after a simple dd
14:40:49 <pwhalen> the f-a-i does extra stuff like copies the ssh key to roots home
14:41:24 <coremodule> f-a-i?
14:42:09 <pwhalen> fedora-arm-installer (sorry)
14:42:18 <coremodule> oh! duh. thanks.
14:42:24 <pwhalen> this is a bash script that is begging to be rewritten
14:42:48 <coremodule> is that different from the arm-image-installer?
14:42:52 <coremodule> https://pagure.io/arm-image-installer
14:43:02 <pwhalen> gah, sorry.. one and the same. we renamed it
14:43:42 <coremodule> lol no worries! want to make sure I know what I'm talking about :)
14:44:29 <pwhalen> but the media writer is likely the easiest for most and will work with the Raspberry Pi's
14:45:39 <pwhalen> does anyone have anything else for today?
14:46:12 <coremodule> alright. thanks for the input. we'll potentially see about getting IoT support in FMW
14:46:39 <pwhalen> coremodule, please feel free to ping me about any of that
14:46:49 <coremodule> thank you! :)
14:46:59 <pwhalen> and you! :)
14:48:23 <pwhalen> #endmeeting