Meeting started at 2025-11-12 18:00:15 UTC

The Meeting name is 'fedora-server'

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

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

!hi

Mat H (theprogram)

Welcome MatH!

Hello, hope you had a good week.

I'll try and stick around here in the long term, not quite sure what I can do in the short-term, but we'll figure something out.

Yeah, I'm sure we can figure out something.

Hi I'm lurking, but I'm not 100% here. Busy with something at the office.

!hi

Jan Kuparinen (copperi)

OK, let's see

Hi Jan!

!hello

Steve Daley (mowest)

Hi Steve!

We are a small group today. Let's see how far we get. But we have our quorum. Let's begin.

Anything to add?

OK

Regarding the action, I'll include the list in our

meetings overview:

Nothing to add

https://docs.fedoraproject.org/en-US/server-working-group/wg-minutes-2025/

Unfortunately, i couldn't manage to compose the list in time. It is a bit longer, currently.

Any additional comment or announcement?

Well, candidate nomination for is open.

For FESCo

We should support our members there.

Is there anyone from our group that is nominated?

Well, Stephen used to be member. I don't know, which seats are for election. We should check. The notification is new from today.

Ok, let's proceed.

https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations

No tracking issue yet

Current public version:

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

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

urrent stg version containing Jocelyn's proposals::

We are missing korora as well as John as well as Emmanuel today. So I don't know, it we can discuss thiss today.

Is there an easy way to see the diffs? I don't use NFS in my homelab so I am not sure what to look for.

It is a long doc

As far as I know we don't have an easy way to look at the diffs. The only way is to use git diff.

I hope, is we get a AsciiiDoc preview in forgejo, we also can manage to get a diff view.

It's a long doc, indeed. The questions are:

- dies the descriptoin result in a working configuration

- is it compatible with our Ansible project. both should produce the same result.

- is it readable and understanble

eh, unless you wrote both you're probably not going to see exactly the third bullet.

Yeah, right.

but the same general idea should apply : a working result

If nobody has an idea, we should postpone

I haven't reviewed it yet except at a glance

Well, let's proceed then

topic 3. Server Docs Contribution work with new Fedora forge

No tracking issue yet

oops

The new thing is my trial to write a Git Cheat sheet for documentation writers.

It is not 100% complete, but about 90%. Question is, can it work for authors?

the way I wrote it.

I think one of the most common things someone is going to run in to is how to commit something to the forge when many of the Fedora contributors are conditioned for SSH-based commits.

Yeah, the issue with the "token"

Getting the token generated and set up with git-credential-libsecret isn't difficult, but you have to know to do it. (Unless you want to be generating a token ever time or insecurely storing that string somewhere)

Paul Maconi (Aggraxis): can you add a chapter about that?

I can add my notes to it. It's very brief.

Brief is OK :-)

The local authoring section is good, necessary, however it is still quite long - any way to reduce word count is great

https://docs.fedoraproject.org/en-US/server-working-group/usr-docs-maintenance/local-authoring/

Well, I'm a sociologist by mayor. 'We usually write a "bit" longer :-)

But every proposal to make it shorter is welcomme.

OK, I see no comment at the moment. You can open an issue as usual. See the upper right corner.

Let's proceed.

no Tracking issue

ok so last week we talked about #114

The LLMNR/mDNS issue

Yes, it is the first of my list here.

Ok so briefly, if we did something impacting beyond just Server we'd need to do a system-wide change proposal. It seems like since we'd be modifying system defaults it might very well be that we have to follow that process instead of the self-contained change.

Also, it looks like zbyszek is the current developer building systemd-resolved in Fedora

I plan on reaching out to him to get his thoughts on the matter and advice for how to proceed

I also have conflicting thoughts on implementation.

OK. I don't know it it is relevant for Server. If you run a server, you will usually have a DNS service.

I can see why you may want to turn this feature off on Server (the llmnr/mdns poisoning attack vector), but I can also see where you might want the responder turned on so that your local LAN clients can find coolserver.local or whatever you named the host.

OK, yes, the responder part.

And on the client side, unless you're on an untrusted network, the likelihood of a poisoning attack is pretty low. When I reinstalled some flavors of Fedora during release testing, several of them picked up my wireless printer via mDNS without intervention on my part.

Which, for the end user, is pretty cool.

The patch submitted to upstream systemd disabled the llmnr stuff by default, but they didn't accept that PR yet.

A couple of other downstream projects did, however, and I didn't see anything resembling a world-ending effect to go along with it.

I would prefer services disabled and higher security on server, and the oposite on workstation

Yes, high security on Server, workstation, I don't know.

Right, so that brings up "how do we effect the change to Server but not anything else"

And I can't answer that yet. I'm hoping a chat with our maintainer will be instructive

Paul Maconi (Aggraxis): you had the idea to include it in post-installation tasks. Would that a short-term solution?

Having this in the recommended post-installation tasks is a solid idea

Informed people may choose not to do it, and that's fine. Uninformed people would at the very least potentially learn something about 'oh, I might not like this behavior'

Paul Maconi (Aggraxis): could you add a section to our post-install documentation?

I am writing an interim summary for the ticket.

Paul, we're counting on you here! 🙂

lol

Let's use the the remaining minutes for open floor!

The floor is open!

Nothing from me, quiet day

OK, obviously nothing. So I close now.

3

2

1