14:01:37 #startmeeting Fedora IoT Working Group Meeting 14:01:37 Meeting started Wed Jul 3 14:01:37 2019 UTC. 14:01:37 This meeting is logged and archived in a public location. 14:01:37 The chair is pbrobinson. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:37 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:01:37 The meeting name has been set to 'fedora_iot_working_group_meeting' 14:01:37 #chair pwhalen pbrobinson bcotton 14:01:37 Current chairs: bcotton pbrobinson pwhalen 14:01:37 #topic roll call 14:01:43 who do we have around today? 14:01:49 * pwhalen is here 14:01:55 * tdawson is here 14:01:56 .hello2 14:01:57 bcotton: bcotton 'Ben Cotton' 14:01:58 * ipcloud is here 14:03:01 we'll give people a minute or so 14:05:01 #topic 1) ==== Working Group process and admin ==== 14:06:01 I have locally a doc written up for phase one and two for Edition promotion, I'll post that likely later today to the docs site and then a link to the list for feedback 14:06:52 pbrobinson++ 14:07:25 I've also been cleaning up various bits that doc mentions, unsurprisingly 14:08:03 there's nothing of real note, we've discussed most of it pretty widely here and elsewhere 14:08:21 bcotton: do you have anything for WG bits? 14:08:38 no sir 14:08:57 i feel like there was something i was going to bring up on the mailing list, but i didn't write it down and i've since forgotten it 14:09:04 OH 14:09:08 i remember! 14:09:41 bcotton: go 14:09:53 bug reports: how people should make them. afaict right now we don't have a "here's the place to report bugs", so we get stuff on mailing list, in chat, people yelling at peter on twitter, etc 14:10:09 do we want to have a "this is the place to go", and if so, what should it be 14:10:53 i'm of the idea that we create an IoT component on Bugzilla, because then it's easy to reassign to other components as needed (e.g. most problems probably aren't IoT-specific,b ut a problem with another package) 14:10:56 that's a good question, we have had some bug reports in pagure, do we get them to go there, and document that in the docs, and then we translate that to where ever it should be? 14:11:08 the downside here is that bugzilla is...not the most user friendly 14:11:41 pagure is an option, too, but it requires bridging issues to BZ when it's a problem with, e.g., the kernel 14:11:41 bcotton: or here? https://pagure.io/fedora-iot/issues 14:12:09 should i take it to the mailing list for further discussion? list out the pros and cons, etc 14:12:27 i don't have a strong opinion either way, since i will be doing very little of the interaction 14:13:20 bcotton: yep, that makes sense 14:13:49 #action bcotton to start discussion on mailing list about bug tracking 14:14:33 pagure is nice to see them all listed together 14:14:40 bcotton: we could also have a page "reporting bugs" which provides options with docs as to what goes where, although that also adds confusion https://docs.fedoraproject.org/en-US/iot/ 14:15:15 pwhalen: problem is you then need a bug wrangler and it can get messy quickly or lost 14:16:15 right 14:16:26 pbrobinson: ack 14:17:31 we have an action for that 14:18:07 #action pbrobinson to publish IoT Edition doc to docs.fp.o and send link to list for feedback 14:18:16 anything else for WG? 14:19:24 nothing from me 14:19:54 #topic 2) ==== Fedora 31 ==== 14:20:23 #info should have rawhide nightlies RSN, I'm just debugging a (probably) signing issue 14:20:55 I noticed they tried to be built 14:21:00 along with all the other things that seem to have landed in the issues pile this week 14:22:04 I've also did a bunch of improvements on Rockchip devices with a focus on IoT and the Rock960 14:22:13 should have docs for that hopefully tomorrow 14:22:14 Ya!! 14:22:48 the display isn't working in U-Boot yet, so currently needs a serial console, but I'm hoping that should be working RSN too 14:23:58 but USB-3 is, as are a bunch of other things and it should be much better in time for beta 14:24:15 very nice, rockchips would be a great addition. who needs a display :) 14:24:40 there's other reasons unrelated to IoT for that TBH 14:26:18 once the compose is done we should better know the status of F-31 14:26:30 #action pbrobinson will send email to the list one the compose is done 14:26:43 anyone else have anything for F-31? 14:28:13 are we planning on sticking with initial-setup in f31? 14:28:27 that is a good question 14:28:40 I need to get some good time with ignition to see if it does what we need 14:29:03 I wonder if we can put it in side by side with initial setup, else I might have to do a special build for testing 14:29:12 I do want to move over if it's sane 14:29:28 I can try to take a look at that 14:30:00 I wonder if it's testable in a general arm image 14:30:10 or general image 14:30:29 #action pwhalen to investigate moving over to ignition and report back 14:30:29 right, no idea.. last I looked it wasnt, but that was quite some time ago 14:30:36 thanks 14:30:41 it's changed quite a bit 14:31:13 good :) 14:31:23 anything else? 14:31:43 * pwhalen has nothing else 14:31:45 #topic 3) ==== Fedora 30 ==== 14:32:11 Fedora 30 will move over to the stable branch with the next release 14:32:16 #info Fedora 30 will move over to the stable branch with the next release 14:32:34 #info that will mean F-29 users will move automatically to F-30 14:32:47 I'll send out an email before that happens 14:33:22 #action pbrobinson to notify the list before F-30 moves to stable branch which upgrades F-29 users to F-30 14:33:40 sounds good, I'll test to ensure no issues when you do 14:33:59 Current F-30 users will need to rebase onto stable, I believe this is a manual flip but I'm still investigating this 14:34:32 pbrobinson: could be a good fedora magazine article, too. a chance to promote Fedora IoT as "what if your devices actually got software updates" :-) 14:35:18 bcotton: good idea, the Edition release will be on the stable branch so once things settle in that regard it should be straight forward for new users there 14:36:16 does any one have anything for F-30? 14:36:30 pbrobinson: i can put together some skeleton content if that'd be helpful. i'll need you/others to fill in the details 14:36:44 bcotton: that works for me 14:38:27 #topic 4) ==== Flock Budapest 2019 ==== 14:39:00 I've put in two talks, one co-presenting with a customer, plus the half day hack fest 14:39:28 has anyone else put any IoT related talks in 14:39:37 or got any queries about Flock? 14:40:16 #topic 5) ==== Open Floor ==== 14:40:18 looks like coremodule and puiterwijk submitted a couple 14:40:29 OK 14:41:10 The only thing I have for Open Floor is that I'll be travelling next week, in Houston, and I don't yet know my meeting schedule 14:41:24 Just want to say I've finally found some time, and I'm testing the mozilla-iot-gateway-container - https://pagure.io/mozilla-iot-gateway-container 14:41:40 so if I'm unavailable pwhalen will be in charge... 14:41:51 tdawson++ cool 14:41:52 pbrobinson: Karma for tdawson changed to 2 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:42:39 pbrobinson: Do you know if you will be going to the Open Source Summit, in San Diego? 14:43:34 tdawson: no, I don't yet, I will be @ OSS Europe, and I'll be at Linaro Connect in San Diego when ever it is in Sept 14:43:59 * bcotton will be at OSS NA 14:45:21 As will I . I'm pretty sure I've met you before bcotton, but it will be good to see you again. 14:45:42 likewise :-) 14:46:10 any one with anything else? 14:47:12 nothng from me 14:47:19 nor I 14:49:11 #endmeeting