14:02:56 <pbrobinson> #startmeeting Fedora IoT Working Group Meeting
14:02:56 <zodbot> Meeting started Wed Feb 13 14:02:56 2019 UTC.
14:02:56 <zodbot> This meeting is logged and archived in a public location.
14:02:56 <zodbot> The chair is pbrobinson. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02:56 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:02:56 <zodbot> The meeting name has been set to 'fedora_iot_working_group_meeting'
14:02:56 <pbrobinson> #chair pwhalen pbrobinson bcotton
14:02:56 <zodbot> Current chairs: bcotton pbrobinson pwhalen
14:02:56 <pbrobinson> #topic roll call
14:03:05 * pwhalen is here
14:03:06 <pbrobinson> yes, it is
14:03:08 <bcotton> .hello2
14:03:09 <zodbot> bcotton: bcotton 'Ben Cotton' <bcotton@redhat.com>
14:03:20 <tdawson> :)
14:03:30 * ipcloud greetings
14:03:30 * laubersm is here
14:03:30 * tdawson is here.
14:04:29 <pbrobinson> #topic 1) ==== Working Group process and admin  ====
14:04:32 <lorbus[m]> .hello lorbus
14:04:33 <zodbot> lorbus[m]: lorbus 'Christian Glombek' <cglombek@redhat.com>
14:04:55 <pbrobinson> #info update on docs
14:05:11 <pbrobinson> laubersm is doing a fantastic job
14:05:19 <alciregi> .hello
14:05:20 <zodbot> alciregi: (hello <an alias, 1 argument>) -- Alias for "hellomynameis $1".
14:05:21 <pbrobinson> do you want to give us an update laubersm
14:05:21 <pwhalen> laubersm++
14:05:27 <laubersm> #info Docs Update:  A lot of the getting started content got updates last week and merged to live over the weekend. I'm continuing with the gaps in those pages and also expanding out the User guide section.
14:05:28 <alciregi> .hello2
14:05:29 <zodbot> alciregi: alciregi 'Alessio Ciregia' <alciregi@gmail.com>
14:05:34 <laubersm> Feedback is welcome. Not just confusion or typos but also what else you would like to see included.
14:05:51 <laubersm> #info Today what I am looking for is what might be called user stories but they do not need to be in any complete format.
14:06:03 <lorbus[m]> laubersm++
14:06:11 <laubersm> These will be used by me in two ways.
14:06:18 <laubersm> #info First, as part of my docs writting for ideas of what content people need to help utilize the IoT images. I would rather describe running a container by using something that is really used rather than just the asciquarrium I set up with podman on my Pi this week.
14:06:30 <laubersm> That said the mozilla gateway is a big larger than than I have in mind :)
14:06:54 <laubersm> So I am looking for Blog posts that you have written or read. or just a simple "I saw X container used for Y activity"
14:06:57 <pbrobinson> #link https://docs.fedoraproject.org/en-US/iot/
14:07:08 <laubersm> This will also help me understand what instruction, if any, would be useful in terms of managing users, networks, remote connections, central logging, security, additional hardware, etc.
14:07:09 <pbrobinson> ##info Today what I am looking for is what might be called user stories but they do not need to be in any complete format.
14:07:17 <pbrobinson> #info First, as part of my docs writting for ideas of what content people need to help utilize the IoT images. I would rather describe running a container by using something that is really used rather than just the asciquarrium I set up with podman on my Pi this week.
14:07:49 <pbrobinson> #info please review and provide feedback
14:08:00 <pbrobinson> overall I think it's looking great
14:08:21 <bcotton> laubersm++
14:08:22 <zodbot> bcotton: Karma for laubersm changed to 3 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
14:09:14 <laubersm> I have been having some fun setting up things.
14:09:20 <laubersm> and reading about what can be done.
14:09:40 <laubersm> The other piece of needing use cases, user stories, and even quotes if for the getfedora pages.
14:09:51 <laubersm> #info I am nudging the design team to help get the inital landing sites drafted out. This would be a page that is added to getfedora mimicing the workstation, server, and atomic workflows:
14:09:57 <laubersm> #link https://getfedora.org/
14:10:01 <laubersm> #link https://getfedora.org/en/workstation/
14:10:05 <laubersm> #link https://getfedora.org/en/workstation/download/
14:10:10 <laubersm> #info We have a starting point for that final download page which is currently
14:10:14 <laubersm> #link https://iot.stg.fedoraproject.org/
14:10:21 <laubersm> #info The getfedora pages will have feature blurbs and can have use case descriptions or quotes (of course with permission). I can help word those but I need a few ideas to work from.
14:10:28 <laubersm> I am getting a pretty good idea of the features including what makes the IoT image different from silverblue and ARM and atomic.
14:10:33 <laubersm> More use case samples would help me.
14:11:03 <pbrobinson> laubersm: the plan was not to add it to the getfedora page but it's own iot.fp.o landing page, IoT is quite a different audience to the rest
14:11:09 <tdawson> laubersm: would you want emails straight to you, or the iot mailling list?
14:11:17 <tdawson> And it's looking wonderful, by the way
14:11:24 <laubersm> tdawson, mailing list would be better.
14:11:27 <laubersm> then all can chime in.
14:11:34 <tdawson> Sounds good
14:11:49 <laubersm> plus depending on what gets done before my contract is up, it is all documented for the volunteers later
14:11:53 <bcotton> laubersm: are you putting docs work on the taiga board (or somewhere else where folks can pick up tasks if they want to contribute)
14:12:54 <pbrobinson> bcotton: we should be migrating instances for tiaga soon
14:13:02 <laubersm> pbrobinson, so there are conflicting things in the open tickets as to what was needed.
14:13:09 <laubersm> https://pagure.io/fedora-websites/issue/788
14:13:46 <pbrobinson> laubersm: lets discuss that offline, can you ping links
14:13:50 <laubersm> the iot one seems to show that this would be at the top level rather than down with other version (ARM, Spins, etc)
14:14:24 <laubersm> #link https://pagure.io/fedora-websites/issue/788
14:14:35 <laubersm> #link https://pagure.io/design/issue/596
14:14:58 <laubersm> the first is a websites ticket. I think is the landing page being pushed out.
14:15:20 <laubersm> the second is a design ticket which I think is how that page looks and maybe intended to be with logos for docs too.
14:15:45 * pbrobinson ceases to actually give a fuck about websites.... when the lead gets completely ignored and the tail begins the wag the fucking dog
14:15:58 <pbrobinson> #topic 2) ==== Fedora 29 release 2 status ====
14:16:28 <laubersm> bcotton, I don't have a list of tasks (yet) but if I can get some ideas out of todays request, perhaps you can help be get them into tasks in appropriate places.
14:16:54 <laubersm> bcotton, I'm a bit out of touch with all the tracking options availble in F these days.
14:16:58 <bcotton> laubersm: sure thing!
14:20:38 * jsmith shows up late... sorry
14:20:46 <bcotton> did we lose pbrobinson?
14:22:02 <pbrobinson> bcotton: no, got interupted
14:22:06 <laubersm> looks like he needed a drink after I brought up websites
14:22:08 <pbrobinson> and I can
14:22:13 <pbrobinson> can't even spell
14:22:31 * bcotton pours a $beverage for pbrobinson
14:22:32 <pbrobinson> laubersm: the whole day I have needed a drink.....
14:22:45 <pbrobinson> sorry s/day/week/g
14:22:46 <laubersm> pbrobinson, so business as usual.
14:22:49 <pbrobinson> right
14:23:05 <pbrobinson> next release, there's been a couple of RC runs
14:23:33 <pbrobinson> #info for those already running F-29 or rawhide IoT you need to run the following commands to rebase
14:24:51 <pbrobinson> ostree remote delete fedora-iot
14:24:51 <pbrobinson> ostree remote add --set=gpg-verify=true --set=gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-iot-2019 --set=contenturl=mirrorlist=https://ostree.fedoraproject.org/iot/mirrorlist fedora-iot 'https://ostree.fedoraproject.org/iot'
14:25:07 <pbrobinson> I'm aware of one bug I'm trying to track down
14:25:38 <pbrobinson> I also think we need to pull in 4.20.8 as it has a bunch of useful fixes and some CVEs
14:25:56 <laubersm> you can shorten that by 4 characters by changing --set=contenturl to --contenturl  :)
14:25:56 <pbrobinson> does anyone have anything else around F-29?#
14:26:09 <pbrobinson> laubersm: ah, OK
14:26:51 <pwhalen> 4.20.8 looks like it has some good fixes, agreed on pulling it in.
14:26:55 <pbrobinson> the images are getting a config error in the repo files and I'm trying to determine where that's coming from an I have another generation error I'm trying to work out
14:28:11 <pwhalen> I also had some issues with the serial console on the rpi3, need to look at it again
14:29:17 <pbrobinson> ah, yes, I need to see if I can recreate that. I have 5 different variants now to test there :-/
14:30:07 <laubersm> pwhalen, let me know when you do. I was trying to make that clearer in the docs and finding things didn't matchup
14:30:21 <pwhalen> pbrobinson, heh.. fun?
14:30:24 <pwhalen> laubersm, will do
14:30:51 <pbrobinson> anyone else have anything for f29?
14:32:07 <pbrobinson> #topic 3) ==== Fedora 30 planning ====
14:32:59 <pbrobinson> so I'm trying to get all the bits finished to get UEFI on ARMv7 enabled so we can enabled it here
14:33:11 * wa1em lurks
14:33:44 <pwhalen> seems very close, if you do a build with those grub2 patches I am happy to test
14:34:07 <pbrobinson> I'm just hoping the wheel for everything will keep falling off everything
14:34:27 <wa1em> wheel for everything?
14:35:04 <pbrobinson> wheel falling off everything
14:35:23 <pbrobinson> tdawson: want to give an update on moz iot?
14:35:41 <tdawson> We have mozilla-iot-gateway in fedora package review
14:35:51 <tdawson> We've already gotten it's one dependency passed and built
14:36:21 <tdawson> I think jsmith would better know how far along the review is, but thus far it's just been a few simple things, licenses actually.
14:36:38 <pbrobinson> yes, I was in front of jsmith on Saturday so the active encouragement helped :-D
14:36:48 <tdawson> As for the two supporting packages ...addons-node and ...addons-python ... I've gotten the -node package done, but haven't gotten it into review yet.
14:36:57 <jsmith> At this point, fixing up the license tag and then figuring out the initscript are the two blockers.
14:37:11 <jsmith> If those two things get fixed, I think I'm ready to approve the package
14:37:29 <tdawson> jsmith: OK ... licesnses should be easy ...
14:37:51 <tdawson> I'm a little worried about the starting script systemd script ... I don't know which user to run it as.
14:38:09 <tdawson> I guess I should put that in the bugzilla
14:38:45 <pbrobinson> tdawson: please link the new deps to the original moz-iot-gw package but using the later as a blocker
14:38:53 <pbrobinson> so they're referenced together
14:39:13 <tdawson> In the gateway image, they run it as pi ... but, I don't want to rely on that user  .... anyway ... ya, I'll dicuss that offline.
14:39:33 <tdawson> pbrobinson: I'm not following ... in the package request bugzilla?
14:39:52 <tdawson> Oh ... the addon-node and python you mean?
14:40:14 <pbrobinson> yes, add on those packages the moz gw review as a blocker in those reviews
14:40:23 <tdawson> pbrobinson: OK, will do.
14:41:38 <pbrobinson> anyone else for f30?
14:42:05 <lorbus[m]> short update on greenboot:
14:43:07 <lorbus[m]> 0.6 is in the works, will be ready today. 0.7 wil follow along shortly after, splitting out some of the essential things that are green/red scripts now into dedicated services
14:43:31 <pbrobinson> lorbus[m]: awesome! Let me know when it's on it's way to rawhide
14:43:35 <lorbus[m]> that'll make it easier to integrate with automatic ostree updates
14:44:20 <lorbus[m]> I will push to the dev branch in a few minutes, I'll tag you on the PR! a short review would be appreciated
14:47:19 <pbrobinson> thanks lorbus[m]
14:47:21 <pbrobinson> #topic 3) ==== Open Floor ====
14:48:48 * jsmith has nothing for the open floor
14:49:09 <tdawson> Just wondering if anyone has looked at the atomic pi ?
14:49:30 <tdawson> It's x86_64 (atom) based, so not arm
14:50:51 <tdawson> I'll take the silence for a no
14:51:30 <pwhalen> hadn't heard it, was just looking at the kickstarter for it
14:52:46 <pwhalen> looks pretty decent at a glance
14:53:33 <tdawson> Usually when they have 'pi' in the name, they try to conform to the pinout of rpi.  They have alot of places you can hook up to it, but as far as I can tell, nothing matches the pi
14:54:43 <tdawson> Don't want to derail if anyone has anything else, was just wondering.
14:54:52 <pbrobinson> tdawson: got a link?
14:54:59 <pwhalen> https://www.kickstarter.com/projects/323002773/atomic-pi-a-high-power-alternative-to-rpi
14:56:46 * tdawson admits he did get one.  I was rather surprised by the power input, or lack of any power input place.  But once I got that figured out, it runs nice.
14:56:54 <tdawson> I haven't tested it against my up2 yet.
14:57:16 <pbrobinson> I have an up²
14:58:12 <pbrobinson> anyone have anything else?
14:59:25 <pwhalen> tdawson, price is definitely nice. Keep us posted on any issues, I might get one as well
14:59:56 <pbrobinson> thank you all
14:59:56 <pbrobinson> #endmeeting