14:01:49 <pbrobinson> #startmeeting Fedora IoT Working Group Meeting
14:01:49 <zodbot> Meeting started Wed Jan  9 14:01:49 2019 UTC.
14:01:49 <zodbot> This meeting is logged and archived in a public location.
14:01:49 <zodbot> The chair is pbrobinson. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:49 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:01:49 <zodbot> The meeting name has been set to 'fedora_iot_working_group_meeting'
14:01:50 <pbrobinson> #chair pwhalen pbrobinson bcotton
14:01:50 <zodbot> Current chairs: bcotton pbrobinson pwhalen
14:01:50 <pbrobinson> #topic roll call
14:01:56 * pwhalen is here
14:01:58 <pbrobinson> who is about?
14:02:21 <jsmith> .hello2
14:02:22 <zodbot> jsmith: jsmith 'Jared Smith' <jsmith.fedora@gmail.com>
14:02:23 * jsmith is here
14:02:24 <bcotton> .hello2
14:02:28 <zodbot> bcotton: bcotton 'Ben Cotton' <bcotton@redhat.com>
14:03:58 <pbrobinson> will give people another minute or so
14:05:10 <pbrobinson> #topic 1) ==== Working Group process and admin  ====
14:05:45 <tdawson> .hello2
14:05:46 <zodbot> tdawson: tdawson 'None' <tdawson@redhat.com>
14:06:05 <pbrobinson> I think one of the things here is we need to improve the getting started docs
14:06:44 <pbrobinson> does anyone else have anything for here?
14:07:15 <tdawson> What sort of things are needed for the getting started docs?
14:07:21 <bcotton> just a +1 to your observation that the getting started docs seem insufficient based on the ML traffic i've seen
14:07:34 <tdawson> I know we need the link to where to download the images
14:07:42 <pbrobinson> #link https://docs.fedoraproject.org/en-US/iot/getting-started/
14:09:05 <tdawson> It would also be nice to have information for each machine that we support, or at least for if there are differences between our generic instructions and what that machine.
14:09:07 * pwhalen is back, brief power outage
14:09:37 <bcotton> and some basic troubleshooting for stuff that comes up pretty often
14:09:44 <bcotton> (i'm being intentionally vague here)
14:09:50 <jsmith> tdawson, bcotton: I couldn't agree more!
14:09:58 * jsmith wishes he had time to write more docs -- many in the next few weeks
14:10:55 <bcotton> i think the ideal end state is that someone like me (who is technical but not particularly familiar with this use case) can go from zero to installed system without having to ask for help
14:11:35 <pbrobinson> tdawson: agreed
14:11:43 <bcotton> if i can get my devconf talks done before devconf (big if), i can do a test run (assuming my first-gen ras pi actually works), but i can't commit to that at this point
14:13:22 <tdawson> bcotton: I think that's a good goal.
14:15:18 <tdawson> One question though ... for arm machines ... I prefer the manual instructions ... is the image install script working consistently yet?
14:16:20 <pwhalen> tdawson, it should be, but I can write it up to include both manual and scripted
14:17:43 <tdawson> pwhalen: It currently has them both, so that is good, it's just that the people having trouble have been using the script ... and I always do it manually, so I'm not positive if it's the scripts problem, or just general problems.
14:17:55 <tdawson> It -> The current docs
14:19:40 <pbrobinson> #topic 3) ==== Fedora 30 planning ====
14:19:46 <pbrobinson> #undo
14:19:46 <zodbot> Removing item from minutes: <MeetBot.items.Topic object at 0x7fe549ece350>
14:19:51 <pbrobinson> #topic 2) ==== Fedora 30 planning ====
14:22:37 <pbrobinson> so I've got some things on the kanban board
14:23:38 <pbrobinson> #link https://tree.taiga.io/project/nullr0ute-fedora-iot/kanban
14:25:59 <pbrobinson> I made a bunch of changes to this, but it appears not to be there
14:26:12 <pbrobinson> if people can't make changes etc do let me know
14:26:36 <pbrobinson> I need to create some epics on the moz iot, uefi on armv7 and a few others
14:26:42 <pbrobinson> anyone else have anything to add
14:26:53 <tdawson> I beleive I can work with tickets that are there, but I don' tthink I can create new one's.
14:27:38 <tdawson> I notice we have ARMv7 containers in Fedora container pipeline ... is that really an IoT thing?  I thought we weren't doing ARMv7
14:28:24 <pwhalen> plan is to add armv7 in f30
14:28:46 <tdawson> Oh ... ok
14:29:04 <tdawson> I guess I can finally pull out all my armv7 machines for something :)
14:29:57 <pwhalen> it was postponed in f29 due to issues with armv7 uefi, that change is again scheduled for f30
14:30:11 <tdawson> OK ... good to know.
14:38:52 <pwhalen> we may have lost pbrobinson
14:39:51 <tdawson> Quite possible ... or else he's gotten lost working on a kanban ticket :)
14:40:26 <pwhalen> heh, I think its his satellite internet
14:41:30 <pwhalen> does anyone have anything else for f30 planning?
14:42:19 <tdawson> Nope
14:43:20 <pbrobinson> sorry
14:43:47 <pwhalen> \o/, was just about to open floor as I dont have the agenda
14:44:02 <pbrobinson> tdawson: we are doing ARMv7, it's been delayed around features, it's wanted from a lot of people
14:44:41 <pbrobinson> anyone else with F-30 queries, requests etc
14:45:28 <pbrobinson> #topic 3) ==== Open Floor ====
14:46:55 <tdawson> I do have one question for open floor.  It's about how often images are made.  Is there going to be just one image per Fedora release?  Or is it going to be more like Atomic Host and have images every so often at a set time?
14:47:26 <pwhalen> I think we talked about every six weeks?
14:47:39 <pwhalen> pbrobinson to confirm
14:47:58 <tdawson> OK, that sounds reasonable, and I seemed to remember something like that, but someone asked me and I couldn't remember.
14:49:06 <pbrobinson> tdawson: the plan is ultimately monthly releases
14:49:22 <pbrobinson> I was planning a 29 release for latish Jan
14:49:53 <pwhalen> ah, thanks pbrobinson
14:50:06 <pbrobinson> the rawhide stuff is mostly nightly, it's broken atm and I need to rebuild the compose host but i think that should be done in the next day or so
14:50:34 <pbrobinson> tdawson: how's the moz iot GW stuff looking?
14:51:28 <tdawson> pbrobinson: I took a break on it during the holidays, although I did play with the release from the moz people.
14:51:59 <tdawson> pbrobinson: I can get it into rpm form, but I'm concerned that it doesn't seem to be written to live in "general" space, only user space.
14:52:50 <pbrobinson> can jsmith potentially assist you with that?
14:53:05 <tdawson> pbrobinson: Yes, I'll need his input for the rpm
14:53:36 <tdawson> pbrobinson: But I think I'll need the moz people's input on what to do if the code is in the global nodejs space and a regular user wants to run it.
14:54:20 <tdawson> pbrobinson: When you talk to the moz people, how do you usually do it?  do you open issues?  Is there an IRC channel and/or mailling list?
14:55:06 <tdawson> *sigh* ... Just saw there is an #iot channel on mozilla.org
14:55:38 <pbrobinson> for those things I generally open an issue
14:55:47 <pbrobinson> I've not had much in the form of tech comms with them
14:55:53 <tdawson> OK
14:56:22 <tdawson> They were pretty quick on my last issue ... hopefully I can get this tested and worded right so they know what my real issue is.
14:57:49 <pbrobinson> OK, great, let me know if I can help
14:57:57 <pbrobinson> does any one have anything else?
14:58:13 * pwhalen does not
14:58:13 <tdawson> Anyway, I think it's coming along pretty good.  I'll contact jsmith this week, as well as the moz team with my issues, and we'll see how it progresses.
14:58:38 <tdawson> I think I've asked everything I had, so nothing more from me.
14:59:37 <pbrobinson> thanks all
14:59:41 <pbrobinson> #endmeeting