Minutes:
https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2025-0…
Minutes (text):
https://meetbot-raw.fedoraproject.org//meeting-1_matrix_fedoraproject-org/2…
Log:
https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2025-0…
=====================================
# #meeting-1:fedoraproject.org: fedora_coreos_meeting
=====================================
Meeting started by @ydesouza:fedora.im at 2025-08-27 15:29:50
Meeting summary
---------------
* TOPIC: roll call (@ydesouza:fedora.im, 15:30:22)
* TOPIC: Action items from last meeting (@ydesouza:fedora.im, 15:33:21)
* INFO: dustymabe replied to the discussion forum thread to
https://discussion.fedoraproject.org/t/proposal-limit-release-blocking-stat…
(@dustymabe:matrix.org, 15:35:01)
* TOPIC: Review Fedora 43 Release Schedule (@ydesouza:fedora.im, 15:37:31)
* LINK:
https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html
(@ydesouza:fedora.im, 15:37:31)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/2010
(@ydesouza:fedora.im, 15:40:51)
* TOPIC: Support Fedora Coreos with Cluster API (@ydesouza:fedora.im,
15:40:51)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1934
(@ydesouza:fedora.im, 15:47:45)
* TOPIC: tracker: Fedora 43 changes considerations (@ydesouza:fedora.im,
15:47:45)
* TOPIC: Open Floor (@ydesouza:fedora.im, 15:52:48)
* TOPIC: Support Fedora Coreos with Cluster API (@ydesouza:fedora.im,
15:55:18)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/2010
(@ydesouza:fedora.im, 15:55:18)
* TOPIC: Open Floor (@ydesouza:fedora.im, 16:19:54)
* AGREED: we think adding CAPI support for Ignition v3 (i.e. CoreOS and
Flatcar) makes sense. We don't have any volunteers to work on it right now
but are looking for some and might have someone in mind for that soon.
(@dustymabe:matrix.org, 16:21:34)
* ACTION: Yasmin Valim de Souza to organize the test week on behalf of
CoreOS. Let's get it scheduled by next wednesday. Hristo Marinov will be
our Fedora QA representative, replacing Sumantro Mukherjee from previous
cycles. (@dustymabe:matrix.org, 16:28:10)
Meeting ended at 2025-08-27 16:32:26
Action items
------------
* Yasmin Valim de Souza to organize the test week on behalf of CoreOS.
Let's get it scheduled by next wednesday. Hristo Marinov will be our Fedora
QA representative, replacing Sumantro Mukherjee from previous cycles.
People Present (lines said)
---------------------------
* @ydesouza:fedora.im (39)
* @dustymabe:matrix.org (35)
* @siosm:matrix.org (21)
* @alicefr:matrix.org (13)
* @zodbot:fedora.im (10)
* @jlebon:fedora.im (7)
* @aaradhak:matrix.org (4)
* @nemric:relativit.fr (3)
* @meetbot:fedora.im (2)
* @hricky:fedora.im (2)
* @mnguyen:fedora.im (1)
* @jbtrystram:matrix.org (1)
--
*Yasmin Valim de Souza*
Associate Software Engineer, CoreOS Engineering
Red Hat <https://www.redhat.com/>
@redhat <https://twitter.com/redhat> @red-hat
<https://www.linkedin.com/company/red-hat> @redhatinc
<https://www.instagram.com/redhatinc>
<https://www.redhat.com/>
<https://redhat.com/options>
Minutes:
https://meetbot-raw.fedoraproject.org/meeting-1_matrix_fedoraproject-org/20…
Minutes (text):
https://meetbot-raw.fedoraproject.org/meeting-1_matrix_fedoraproject-org/20…
Log:
https://meetbot-raw.fedoraproject.org/meeting-1_matrix_fedoraproject-org/20…
=====================================
# #meeting-1:fedoraproject.org: fedora_coreos_meeting
=====================================
Meeting started by @marmijo:fedora.im at 2025-08-20 15:30:58
Meeting summary
---------------
* TOPIC: roll call (@marmijo:fedora.im, 15:31:04)
* TOPIC: Action items from last meeting (@marmijo:fedora.im, 15:35:23)
* TOPIC: Review Fedora 43 Release Schedule (@marmijo:fedora.im, 15:41:22)
* LINK:
https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html (@marmijo:
fedora.im, 15:41:29)
* INFO: branching has already occurred. The FCOS branched stream is now
enabled tracking F43. (@marmijo:fedora.im, 15:43:43)
* INFO: next event is 'Beta Freeze', scheduled for 2025-08-26 (@marmijo:
fedora.im, 15:43:52)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1935
(@marmijo:fedora.im, 15:45:07)
* TOPIC: Proposal: Limit release-blocking status of BIOS systems to just
certain scenarios (@marmijo:fedora.im, 15:46:35)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1987
(@marmijo:fedora.im, 15:46:39)
* LINK:
https://discussion.fedoraproject.org/t/proposal-limit-release-blocking-stat…
(@marmijo:fedora.im, 15:49:48)
* AGREED: We will respond in the discussion forum thread on this topic.
Generally we don't see an issue with Fedora QA dropping manual testing of
CoreOS+BIOS because we have CI that covers this use case and a once a
Fedora cycle test day that covers manual testing for it. (@marmijo:fedora.im,
16:15:11)
* ACTION: dustymabe to respond in the discussion forum thread stating
that the CoreOS team does not see an issue with the proposal to drop manual
testing of CoreOS+BIOS because we have CI that covers this use case and a
once a Fedora cycle test day that covers manual testing for it. (@marmijo:
fedora.im, 16:15:19)
* TOPIC: Introducing the fcos-assistant Bot (@marmijo:fedora.im, 16:16:43)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1999
(@marmijo:fedora.im, 16:16:48)
* TOPIC: Open Floor (@marmijo:fedora.im, 16:30:12)
Meeting ended at 2025-08-20 16:41:33
Action items
------------
* dustymabe to respond in the discussion forum thread stating that the
CoreOS team does not see an issue with the proposal to drop manual testing
of CoreOS+BIOS because we have CI that covers this use case and a once a
Fedora cycle test day that covers manual testing for it.
People Present (lines said)
---------------------------
* @dustymabe:matrix.org (62)
* @marmijo:fedora.im (32)
* @jlebon:fedora.im (16)
* @spresti:fedora.im (7)
* @zodbot:fedora.im (7)
* @aaradhak:matrix.org (6)
* @meetbot:fedora.im (2)
* @hricky:fedora.im (2)
* @ydesouza:fedora.im (1)
* @alicefr:matrix.org (1)
Hi Team,
I'm part of the Qualys Security Research Team. We actively monitor and analyze vulnerabilities across various operating systems to help our customers maintain strong security postures.
We’ve had mutual customers who are using Fedora CoreOS in their environments and have requested that we provide vulnerability coverage and detection support for it within our platform. We’ve also conducted our own initial internal research to identify security advisories related to Fedora CoreOS, but so far we have not been able to locate a centralized or official source of such advisories—especially those related to CVEs or package-level vulnerabilities.
We understand that Fedora CoreOS leverages components from Fedora and uses technologies like rpm-ostree and Zincati, but due to its unique update model, it would be helpful to have clear guidance on how to track security updates specific to Fedora CoreOS releases.
Are these advisories published publicly, or are they tracked internally within the Fedora project? Any assistance or direction you can provide would be greatly appreciated.
Thanks,
Siddhant Bharat Gawai
Qualys Security Research Team
Qualys, Inc.<https://www.qualys.com/>
Minutes:
https://meetbot-raw.fedoraproject.org/meeting-1_matrix_fedoraproject-org/20…
Minutes (text):
https://meetbot-raw.fedoraproject.org/meeting-1_matrix_fedoraproject-org/20…
Log:
https://meetbot-raw.fedoraproject.org/meeting-1_matrix_fedoraproject-org/20…
=====================================
# #meeting-1:fedoraproject.org: fedora_coreos_meeting
=====================================
Meeting started by @marmijo:fedora.im at 2025-08-06 15:30:05
Meeting summary
---------------
* TOPIC: roll call (@marmijo:fedora.im, 15:30:11)
* TOPIC: Action items from last meeting (@marmijo:fedora.im, 15:38:42)
* TOPIC: Review Fedora 43 Release Schedule (@marmijo:fedora.im, 15:41:25)
* LINK:
https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html (@marmijo:
fedora.im, 15:41:36)
* INFO: Fedora 43 branching event happening on 2025-08-12. Rebase
checklist items for branching to be started/completed this week. (@marmijo:
fedora.im, 15:45:57)
* TOPIC: Platform Request: UpCloud (@marmijo:fedora.im, 15:46:29)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/2000
(@marmijo:fedora.im, 15:46:37)
* INFO: A discussion was had about the ever-expanding number of build
artifacts. A tracker issue was made to discuss reducing the frequency of
generating all artifacts for the dev and mechanical streams. See:
https://github.com/coreos/fedora-coreos-pipeline/issues/1189 (@marmijo:
fedora.im, 16:18:36)
* AGREED: Support UpCloud as a full platform for Fedora CoreOS. Some
clarifying questions have been added to the ticket, but the platform is
considered conventional and should not be difficult to support. We'll view
https://github.com/coreos/fedora-coreos-pipeline/issues/1189 as a
prerequisite for supporting the new platform. (@marmijo:fedora.im, 16:33:08)
* TOPIC: Open Floor (@marmijo:fedora.im, 16:33:53)
* INFO: oraclecloud made it to stable now! (@dustymabe:matrix.org,
16:34:36)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1967
(@marmijo:fedora.im, 16:35:12)
Meeting ended at 2025-08-06 16:35:41
Action items
------------
People Present (lines said)
---------------------------
* @dustymabe:matrix.org (37)
* @marmijo:fedora.im (35)
* @jlebon:fedora.im (19)
* @spresti:fedora.im (14)
* @zodbot:fedora.im (5)
* @meetbot:fedora.im (2)
* @aaradhak:matrix.org (2)
* @hricky:fedora.im (1)