Meeting started at 2025-10-29 17:00:29 UTC

The Meeting name is 'fedora-server '

As usual, let's wait a moment for everybody to show up.

I'll post the agenda in 2-3 minutes.

!hello

Emmanuel Seyman (eseyman) - he / him / his

Hi, Peter !

!hi

Paul Maconi (aggraxis) - he / him / his

Hi Emmanuel Seyman Be careful not to get the keyboard wet.

Hi Paul, good to meet you!

hi!

!hi

Jocelyn Gould (korora) - she / her / hers

Welcome Jocelyn (she/her)

I see, nirik is lurking as usual, so we should start noe.

Anything to add / remove /something else?

OK let's start

Regarding the action, nothing new. See

We had some unexpected issue with our staging user documentation. It was still fed from pagure. We finally fixed it yesterday. I hope we've ironed out all thwe kinks now. Let's see.

Awesome

Yes, that's good to hear

Anything else to announce?

OK let's go on

Max 10 mins

Tracking issue: !link https://pagure.io/fedora-server/issue/164

Max 10 mins

Open discussion about our experiences with this release.

The server images did fine for x86_64 installation and testing

I didn't have any issues, and my upgrades this week went well.

Yes, at least the x86_64 installation images are really stable and robust.

In my memory, we didn't work enough on the specific risks, i.g. the backward-incompatible changes in Dovecot or the version change in Postgres.

We should pay more attention to this part next time.

And the problem with the SBC installation once again took up a disproportionate amount of time. I can't think of any way to improve it.

I haven't moved anything else to 43 yet.

I did install 43 workstation and the only thing I've noticed is I have a few extensions that don't work...

Well, Workstation changes a lot. In this release dropping the X11 server and use exclucvely Wayland.

But that's not our style, fortunately. We only change what really brings progress.

Anyway, are we satisfied with how things went with F43?

We have there a 3 years old ticket: https://forge.fedoraproject.org/server/tickets/issues/63

And an unfinished discussion about it. And some planning to improve the test notification and maybe start a Test Work.

I'm sure there are more tests to automate, which will hopefully free up more of our time

The only non-automated tests are the installation tests on hardware, and checking that the installation documentation is up to date.

I need to set up my environment to work on docs still.

I did virtual bios and uefi and hardware uefi installs for several builds

1.6 happened while I was without connectivity, but 1.5 passed happily

Paul Maconi (Aggraxis): Yes, previously the hardware side depended solely on me, until this time.. This time it would have gone wrong because of the SBC problems.

Question is, ,do we want to stick to the plan of systematizing/improving/simplifying our release testing and initiate a test week? And if so, who would take care of it?

I could write a summary of our discussion so far. As a kind of initial spark, so to speak. But then someone would have to take over.

FTR, I really would like to focus on post-installation tasks

FTR? (sorry

FTR: Fr the Record

The installation testing is largely automated aside from a bare metal install, and then a lot of the cases we're not hitting are "weird storage"

Thanks!

Like who has a SAS controller handy, etc.

Yeah, and there are some types of issues, you can only see in reality, e.g. those issues with the blivet UI.

I do, but not in a machine that I can use for testing... (although I do have a spare server, but not a way to really *use* it

I have one too, but it's in a server that's doing stuff (being a hypervisor for a bunch of fedora vms, the way nature intended...:P)

I have a lot of spare servers, unfortunately for me, so I have the hardware to do all the tests. 😒

Question still is: "The WG will continue testing new releases as is and abandon further planning." or Or shall we discuss this further as part of our work planning? (discussing such a plan is necdessary anyway, I thing).

Perhaps we can agree that Peter Boy (ServerWG, Docs) should write a summary to the list and we should see where the discussion takes us

I will have to dig my R410 out and fire it up for testing purposes

Emmanuel Seyman: that would be OK, and than we should have a working plan discussion. What do you think about that?

We should proceed with the next topic. At the meantime:

Sounds like a good option to me

topic 3. Server Docs: How to proceed with NFS doc

o tracking issue yet

Current public version:

https://docs.fedoraproject.org/en-US/fedora-server/services/filesharing-nfs-installation/

No tracking issue yet

I use NFS on my network, I can take a look at the docs on it

In staging version:

https://docs.stg.fedoraproject.org/en-US/fedora-server/services/filesharing-nfs-installation/

Jocelyn (she/her): Great.

When you say how to proceed

These is also an idea, to split the

What are you looking for? Just to update it?

Yes, to update if necessary, to fix it if something doisn't work as decribed or to add some description.

And we had the idea, to split into installation and administration.

There's a PR against that page on the new forge

And there is a plan to discuss with abbra to integrate some "key-thing" to inable an easy way to provide the login facility of version 4

abbra: gave a talk on this year FOSDEM about that. I don't remember the details out of my head.

But Emmanuel Seyman probably does?

(I mean remember the details)

Keycloak ?

Yeah, sounds right.

!hi

Mat H (theprogram)

Welcome MatH

I don't remember anything NFS-related in FOSDEM's IAM track

The track : https://archive.fosdem.org/2024/schedule/track/identity-and-access-management/

Are you talking about #137?

No, #174

!hello

Steve Daley (mowest)

Well, #137 ist still open, too.

So, both are to deal with.

hey steve :)

OK, let's start with the current open issues, and I will contact abbra about that key-talk he made at FOSDEM and how to make it usable in Server.

Let's move on for now.

Ah, issue #137

PR #174 fixes the issue #137

i'll look both

Alright, two birds with one stone.

Our time is nearly up. So I think, we skip the walkthrough again.

Anything to discuss / announce / comment here?

Sorry, I'm late to the party again. Thanks for continuing the great work. I'm hoping to finish upgrading all my machines to F43 this week and weekend.

mowest: Welcome anyway!!!!!!! Glad to meet you.

OK, nothing for the moment, so let's close in time for once (And Emmanuel can dry the bike and the wet clothes)