Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-27/fedora_coreos_meeting.2022-04-27-16.30.html Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-27/fedora_coreos_meeting.2022-04-27-16.30.txt Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-27/fedora_coreos_meeting.2022-04-27-16.30.log.html ======================================== #fedora-meeting-1: fedora_coreos_meeting ======================================== Meeting started by dustymabe at 16:30:24 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-27/fedora_coreos_meeting.2022-04-27-16.30.log.html . Meeting summary --------------- * roll call (dustymabe, 16:30:29) * Action items from last meeting (dustymabe, 16:36:24) * jlebon reached out and we have reps from the nmstate here with us today (dustymabe, 16:36:45) * jaimelm and dustymabe met with Fedora releng/infra to discuss forward strategy for Fedora container hosting. The goal is to get off of their own infra and onto quay.io (https://pagure.io/fedora-infrastructure/issue/10386), thought they have some open questions about if flatpaks can be hosted there. (dustymabe, 16:37:21) * We are going to all work together over the next week to try to chase down any open questions and then move forward with putting our FCOS containers in quay.io if no blockers are found. (dustymabe, 16:37:38) * This will lead Fedora's transition to quay.io by some months, but the releng/infra team feels it's best if we start there for new containers rather than go to the old infra right before a transition. (dustymabe, 16:37:49) * New Package Request: nmstate-libs and nmstate (dustymabe, 16:39:58) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1175 (dustymabe, 16:40:03) * AGREED: nmstate is useful for dynamically configuring a running system OR generating NM keyfiles with no running system needed. The nmstate YAML config itself can't be used on system boot without an accompanying service to apply the config. In order to use it for provisioning a user would need to write a systemd unit themselves to apply the config they wrote using Ignition. At this time (dustymabe, 17:33:05) * open floor (dustymabe, 17:35:58) * LINK: https://discussion.fedoraproject.org/t/automated-fedora-coreos-35-for-raspberry-pi-4-b-400/38359 (aaradhak[m], 17:36:34) * we will be having our FCOS community video meeting next Wednesday at https://meet.google.com/meo-enbb-rur?hs=224 (dustymabe, 17:39:18) Meeting ended at 17:41:03 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (87) * zodbot (27) * ffmancera (26) * jlebon (25) * walters (22) * thaller (18) * lucab (11) * aaradhak[m] (4) * miabbott (2) * jbrooks (1) * gursewak (1) * saqali (1) * aaradhak (1) * jaimelm (1) * ravanelli (1) * mnguyen (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
