IoT July 2020

iot@lists.fedoraproject.org

4 participants
12 discussions

Website content
by Ben Cotton 09 Oct '20

09 Oct '20

In order to put a page on getfedora.org, we need something to put there. I'm happy to craft it into Content™, but I need your help in coming up with ideas. This will also help me let the Design team know what kind of art we need for it. See the Workstation and Server pages for an idea of what I'm looking for: https://getfedora.org/en/workstation/ https://getfedora.org/en/server/ What are 3-5 short (1-5 words) phrases we can use as key themes? -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

4 7

[Fedocal] Reminder meeting : IoT Working Group weekly meeting
by pbrobinson＠fedoraproject.org 28 Jul '20

28 Jul '20

Dear all, You are kindly invited to the meeting: IoT Working Group weekly meeting on 2020-07-29 from 14:00:00 to 15:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Fedora IoT weekly status meeting. More information available at: [https://pagure.io/fedora-iot/](https://pagure.io/fedora-iot/) Source: https://apps.fedoraproject.org/calendar/meeting/9245/

1 0

[Fedocal] Reminder meeting : IoT Working Group weekly meeting
by pbrobinson＠fedoraproject.org 28 Jul '20

28 Jul '20

1 0

package layering: solving the base layer yum repo out of sync problem
by Dusty Mabe 27 Jul '20

27 Jul '20

Hello Silverblue and IoT teams. The FCOS team got together with Fedora releng last week to discuss the issue regarding package layering that periodically plagues us (https://github.com/coreos/fedora-coreos-tracker/issues/400). The solution we believe will help all OSTree based editions involves creating an archive repo where any package that has made it to the Fedora stable repositories can be accessed at a later time. In general, we think this should solve the problem because we should be able to install packages that won't require updating the base layer. Goals: - help solve the same problem for Fedora CoreOS, Fedora Silverblue, and Fedora IoT - don't add to mirror network requirements - i.e., store/host the content somewhere else. AWS is a candidate here. - keep traditional systems behavior the same - don't enable archive repo(s) by default on non-ostree distributions Since it can take a long time to create repos for large package sets we may end up creating more than one repo that gets updated at different cadences. For example: - One that gets updated weekly - all packages obsoleted before X date - large package set, so we run it once a week - One that gets updated nightly - all packages obsoleted after X date - small package set, so we can run it nightly This is still a work in progress and the design may take a few turns as we work out the details and/or find new information. Having this new repository will help us in Fedora CoreOS as we have a stable stream that lags behind Fedora stable repos. It should also help Fedora Silverblue when they move to a release cadence that doesn't match the bodhi updates repos. I'm not sure how much of a problem this currently is in Fedora IoT, but I imagine Fedora IoT has similar problems. Thoughts? Dusty Mabe

1 0

Improving our Product Requirements Document
by Ben Cotton 27 Jul '20

27 Jul '20

In order to meet what will probably be the requirements[1] for promotion to an Edition, we need to add some content to our Product Requirements Document[2]: - Core services & features - Core applications - Unique policies for installation, updates, etc This information will help the QA team make sure they have good test cases, marketing help know what to talk about with IoT, etc, etc, etc. So...uh...what should we add? [1] https://fedoraproject.org/wiki/Editions/Promotion_Process [2] https://docs.fedoraproject.org/en-US/iot/prd/ -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

1 1

Orphaning two packages
by Troy Dawson 23 Jul '20

23 Jul '20

I have not been able to give mozilla-iot-gateway the attention that it needs. Also, upstream now has Fedora rpm's[1], and a container, so having it in Fedora is not as critical as it once was. Below is the packages I am orphaning: mozilla-iot-gateway nodejs-nanomsg There is nothing that depends on them. Troy Dawson [1] - https://github.com/mozilla-iot/gateway/releases

1 0

[Fedocal] Reminder meeting : IoT Working Group weekly meeting
by pbrobinson＠fedoraproject.org 21 Jul '20

21 Jul '20

Dear all, You are kindly invited to the meeting: IoT Working Group weekly meeting on 2020-07-22 from 14:00:00 to 15:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Fedora IoT weekly status meeting. More information available at: [https://pagure.io/fedora-iot/](https://pagure.io/fedora-iot/) Source: https://apps.fedoraproject.org/calendar/meeting/9244/

1 0

[Fedocal] Reminder meeting : IoT Working Group weekly meeting
by pbrobinson＠fedoraproject.org 21 Jul '20

21 Jul '20

1 0

[Fedocal] Reminder meeting : IoT Working Group weekly meeting
by pbrobinson＠fedoraproject.org 14 Jul '20

14 Jul '20

Dear all, You are kindly invited to the meeting: IoT Working Group weekly meeting on 2020-07-15 from 14:00:00 to 15:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Fedora IoT weekly status meeting. More information available at: [https://pagure.io/fedora-iot/](https://pagure.io/fedora-iot/) Source: https://apps.fedoraproject.org/calendar/meeting/9245/

1 0

[Fedocal] Reminder meeting : IoT Working Group weekly meeting
by pbrobinson＠fedoraproject.org 14 Jul '20

14 Jul '20

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

IoT July 2020