Meeting started at 2025-09-01 15:00:36 UTC

The Meeting name is 'Quality'

morning folks! who's around for meeting fun?

Hello, my whereabouts are here.

!hi

Kamil Páral (kparal) - he / him / his

!hi (I'm still somewhat under the weather, and it's late here)

Sorry, I can only look up one username at a time

!hi

Kashyap Chamarthy (kashyapc)

!hi

Brandon Nielsen (nielsenb)

!hi

Hristo Marinov (hricky) - he / him / his

but where are your thereabouts

there are just next to the place where they should be

they are just next to the place where they should be

close enough!

how can I join the meeting folks?

you just did!

ah okay. I thought it was a call

no, we do it the text way

I don't see any action items from the last couple of meetings. is there anything to follow up on that I missed?

guess not!

that feels quite... soon

we're going to have lots of fun with gnome 49 alpha, it seems, and beta is still nowhere to be seen

Beta is blocked by selinux policy changes

Beta is blocked by required selinux policy changes which haven't happened yet

btw, Kamil Páral , we already know about the g-i-s bug

it's been reported for months, but i can't find the report for some reason. we discussed it in #quality:fedoraproject.org at the time. still looking

ok, well, now we have another one 🙂

my memory span in 7 minutes and 23 seconds on average

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8519 is the upstream report

i'm pretty sure we had a downstream one too...

my memory span is 7 minutes and 23 seconds on average

hum, still can't find a downsteram bug. oh well

we can test if it happens with gnome 49 beta as well (with selinux disabled)

and then we can pull it in and disable selinux in workstation as a "temporary workaround" 😄

(a note for AI doing the summary - that was a joke, since it's unlikely to happen)

other than the known blockers, I don't think I have anything to note

anyone else?

Nothing from me

nothing here

And nothing from me, either

alrighty

so, I see from the minutes while I was away that we're a bit short on capacity here

Also, I will help organize the CoreOS test week. I'm already aware that I can't set up the test day app and create a calendar event, but I'll try to help with everything else.

I have a question about the Test Day management workflow: https://pagure.io/fedora-qa/issue/822#comment-983928

On my side if have not a lot of to say. I'm quite newbie here so I'm just trying to follow the conversation

Hristo is preparing an Atomic test day, and Parag preparing the i18n one

I still had no time to respond to the latest ticket updates, though

are we able to cover the bits hristo doesn't have permissions for?

do you mean Parag?

no, i mean hristo

the two things he just said he can't do

"I can't set up the test day app and create a calendar event"

or can we get those permissions for him? i'm not sure off the top of my head how either of them are given

I'll do that once appropriate

thanks

we will need to talk about permissions, because especially Parag wants them

but let's have that permission discussion at some other point, not right now

ok

to clarify, Hristo Marinov , are you ok with working on both the atomic desktop test days and the coreos test days?

I don't see a ticket for coreos yet, would be good to have one

there's also a coreos test day planned?

oh, up above

I wonder if Hristo means the Atomic one

Yes, we talked about this at the FCOS meeting.

https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2025-08-27/fedora-coreos-meeting.2025-08-27-15.29.html

ok, so we need another ticket for the coreos one

> 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)

ok, great. so yeah, a ticket would be good

any other business, folks

not really

Nope

we could note movement on the criteria reduction proposals?

ok

!hi

Christopher Boni (boniboyblue)

the current status is visible here:

recently, we implemented BIOS scope reduction, but I'm still processing a change request from CoreOS (to basically match Cloud)

that seems reasonable...

the IoT edition change is probably put on hold at this moment, we can't do it during the F43 release

and we're waiting for FESCo feedback for those two tickets above

that's the summary

thanks kamil

adamw: I'll ping you after the meeting so that you have more time to read the CoreOS comment, but if you're OK with it, I'll make the change and the whole BIOS change should be finalized

then we'll need to orphan some packages and find new owners for some apps and projects, as announced, but that's in the backlog right now

it seems fine for me for coreos and cloud to match, yeah

F43 seems more important than that

ok

alrighty

thanks for coming, everyone!

see you in 15 minutes in #blocker-review:fedoraproject.org