Meeting started at 2026-07-15 17:00:04 UTC

The Meeting name is 'fedora-server '

!group members server-wg

Members of server-wg: Alexander Bokovoy, Adam Williamson, Paul Maconi, Emmanuel Seyman, jwhimpel, Kevin Fenzi, korora (@korora:fedora.im, @korora1981:matrix.org), mowest, ngompa (@conan_kudo:matrix.org, @ngompa:fedora.im, @pharaoh_atem:opensuse.org, @ngompa:kde.org, @ngompa:almalinux.im), Peter Boy, Stephen Gallagher

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

Welcome to our weekly Server WG meeting.

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

!hi

Ro: Rowan Puttergill (goroboro) - he / him / his

!hi

Sorry, could not get info from FASJSON (code 500)

Did it not like me? Lol

Oh, zodbot again

mmm not sure what FASJSON is about

!hi

Sorry, could not get info from FASJSON (code 500)

I cry

It had the same issue earlier at Council meeting

ah... it is [Brett](https://matrix.to/#/@brettweir:matrix.org) - zodbot does not love you

it's probibly under attack. will look.

I always knew zodbot felt this way

it didn't like what you were thinking about for your wiki profile :P

I hadn't even told it yet! Not even fair

zodbot knows all!

Reminds me of zombo.com lol

that was epic

ooooh zombo.com has been updated

there is singing!

Hm, we still miss at least two formal members, but let's start anyway. Someone may join us later. And otherwise we can't make decisions.

I'll post the Agenda

Anything to add or to remove?

OK. Let's start

Looks pretty good to me!

Regarding the action, see the list in our

meetings overview:

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

Did I forget something?

Nothing I am aware of

Announcements:

Has someone something to announce?

Nothing from me today.

Nothing from me.

Let's proceed

Not from me

Tracking issue: https://forge.fedoraproject.org/server/tickets/issues/203

We are lacking behind here.

Today, a new test release came out.

I created some issues as discussed:

https://forge.fedoraproject.org/server/tickets/issues?q=&type=all&sort=relevance&labels=583&state=open&milestone=0&project=0&assignee=0&poster=0

And a project:

https://forge.fedoraproject.org/server/tickets/projects/615

I have to add tickets for UEFI.

What do you think about it?

That looks really good Peter. Using this, I might actually get involved in testing because it is easier to see what is going on

hopefully we have folks willing to do those tests. ;)

and yeah, could work nicely for rc's and such too...

Yes, it's a lot of manual editing, at the moment.

We need to find a way to automate the process of issue generation a bit.

It will definitely make sense to template this all in future... and maybe automate

Yeah, I'd want to set up a little device farm at my house to exercise lol

But I really like this - perhaps because I came from a Jira driven environment where everything was ticketed and tracked in a Kanban board.... this feels familiar to me.

Any proposal to improve the ticket contents?

Otherwise I would add the missing 4 tickets later today.

might link to the test plans on the wiki?

It would be great to get a little mentorship around the expectations for testing etc. If it is just a case of following the document end to end and noting anything that doesn't work... that's all good. If it is a case of identifying changes - we should have a process for spinning off a doc update.

I would only say that I haven't done this testing before and I'm curious to try. I agree with [Ro](https://matrix.to/#/@goroboro:matrix.org) it's quite accessible.

Oh yes, on the wiki is better. The problem is to update the links with each new released build.

Well, we should add findings to comments, specifically the required update of the docs.

And of course, what is wrong. E.G. with the KVM image still has wrong file system tyopes

for the issues might be good to file as bugs in bugzilla... that way they can be nominated as blockers, etc.

Yes, indeed, and logged in the ticket not to forget them. :-)

I am keen to help out with some of the testing, but some guidance on what I should be doing might be handy... maybe I just need to ask questions in the [\#server:fedoraproject.org](https://matrix.to/#/#server:fedoraproject.org) channel

Yes, the Server channel is the place to ask. And I will add links to the test descriptions, and probably some more informations.

I definitely need to pick off less critical stuff since it is my first attempt at this

So wrapping up:

Proposal: !agreed The WG will start with the F45 test tickets in their current form and to adapt them as necessary during the testing process.

Objections?

+1

+1

Nope, +1

Next topic

!helo

No tracking ticket yet

!hello

Emmanuel Seyman: Emmanuel Seyman (eseyman) - he / him / his

Hi Emmanuel!#

Sorry I'm late, folks

Oh lol is zodbot working again?

!hello

We decided for individual development environments. But didn't had decided about how to do.

Who writes a first documentation how to install and configure a dev env ?

Or:

There was some discussion at

https://discussion.fedoraproject.org/t/create-a-custom-fedora-linux-spin-using-kiwi/194519

Do we have a communication specialist who can try to involve or get some advice from that discussion?

I'd be happy to poke around. I have more experience using debian multistrap and kickstart, but I imagine I can figure it out.

I really want a CI/CD environment for this kind of work though, as it provides the best documentation, but the Forge runners can't support it, so I've been building a ForgeJo runner at my house.

you can look at the official kiwi descriptions for inspiration...

https://forge.fedoraproject.org/releng/kiwi-descriptions/

Brett: For the first step we have to use a dev env outside of forge. So, at the moment no CI. That's the second step, when we have something up and running.

We need a guide, how to set up our devenv each and how to do the basic configurations.

I'm happy to put a local dev env together for this anyway. I can start on a fresh machine and write up the setup process.

I did that for the previous tool (already forgot the name)

Brett: that would be great!

braver man than me :D

Is there a project already created? If not, can I get one to make PRs into?

proposed. !action Bred will set up a dev environment and document the process so that others can follow suit.

I still have to create the repo. Will that later today!

proposed. !action Brett will set up a dev environment and document the process so that others can follow suit.

Okay, excellent, I love setting up a project from scratch. 🙂

OK, then:

I think, that's all about this for today.

Tracking issue: https://forge.fedoraproject.org/server/tickets/issues/210

Wouldn't is be useful to add an article / Server specific style guide?

Theoretically... we should make sure that the style guide is up to date: https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/style-guide/ -- I mean.... we should all try to adhere to a common style as much as possible

I think that's a good idea where we have deviations or use cases not covered by the main style guide. Even just having a page that says "We follow the main style guide but we also do this, this, this"

That's the general style guide. We have some additions, e.g. the !"editor war" or shat we decided about adochere (I alredy forget it)

A page in the wg docs or something

Ro: You did a lot in this area. Could you write a first version. It will be short at the moment, I think.

In the spirit of "upstream first", we should evaluate whether our style decisions belong in the general style guide

okay... I guess that makes sense...

yeah, a docs page seems reasonable. or... info on server docs repo for people submitting? or both?

(on an ongoing basis)

I could put something together.... maybe just info on the server docs repo?

nirik: Yes, we should have a link at the repo description

Ro: Yes, just about the specifics, we add apart from the general docs, or where we make a specific selection.

I will take a look... and see if I can draft up a file... I will do it in my fork and submit a PR and you can tell me to put it somewhere else if that makes sense.

OK, then

I am sure I will be missing things... but at least it will be a start.

proposed. !action Ro will draw up an initial draft of documentation setting out the server-specific additions to the Docs Style Guide.

IS that OK?

+1

+1

OK, next one.

No tracking issue yet

All our contribution docs have a note: "outdated". 😒

Maybe we discuss this on our Server room for now?

I think everybody of us has already a job to do.

which docs are these?

hehehe, whichever you like. There are parts I've encountered that seem out of date. Or indicate that they're out of date when they may not be.

Oh, I'm thinking of server docs though.

This docs:

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

and the articles beyond that one

Oh, I see there's still mention of pagure.io on https://docs.fedoraproject.org/en-US/fedora-server we should fix all those. ;(

oh, I'm sensing some style-related PRs in the future 😆

I think the main issue is to fix the pagure links and the pagure way for online editing.

OK, I think:

Well, let's skip the walk through old issues and use the remaining time for open floor.

Some contribution here? The floor is open, for anything

Just a notice that I resolved that dnsmasq PR conflict... so you should be able to merge

I'll do the merge later today.

I will try to add some more on this... but I am now jumping around on quite a few things... so new content is probably a side project

I want to incorporate some of what I've written lately into the server docs. Would everyone be okay if I contribute an article on using mDNS or Ansible with Fedora? Repackaging some of the content from that codeberg site I was working on.

Brett: That would be perfect. So we can discuss something real.

No objections from me... I think that Ansible is excellent

I think, we should shortly reflect about our projects.

The home servcer spin is running, more or less. There is the Ansible project, which is still stepping in place, there is the strenghening updates project, w/0 progress at the moment, streamline backup&restore, and LocalKDC.

With the later there is some progress, too.

Emmanuel Seyman: Do you have something new?

No, I'm still working through my packaging issues

With the Strengthening Server updates project, I had some discussion at flock. But couldn't manage to make some progress here

The end is in sight...

I feel like Fedora Server has a lot to offer. My favorite thing about it is how current distro-native packages are. It makes it much easier to get started with a reasonable setup. I want to capture that feeling in our documentation.

Emmanuel Seyman: Can we put it on the agenda next meeting or in 2 weeks?

It's so nice to not be spending all my time wget && curl && bash && install from everywhere and never knowing if it's up-to-date

put what on the agenda?

Brett: yes, we should emphasise the Fedora specific properties !!!!!!

on the agenda for the meeting.

Emmanuel Seyman: on the agenda for the meeting.

I have to drop off... I think I have things to pick off this week... will check in later

I'm quite sure, I'll have nothing new with the Strengthening Server updates project, unfortunately.

Put the Ansible project on the agenda in 2 weeks

I'll try to get something together in 3 weeks.

Yeah, our time is up. So. I'll close now. Let's continue in our Matrix room.

Hm, zodbot ??????

RIP zodbot

It never even had a chance to say !hi to me...

hum...

Brett: can you do a !hi...

!hi

Emmanuel Seyman: Emmanuel Seyman (eseyman) - he / him / his

!hi

Brett: Brett Weir (brettweir) - he / him / his

I feel seen!

huh, ok... lets try:

zodbot loves us so much, we will not end it. 😀

great. ;( It's erroring, but I don't see why yet. will keep digging

It's okay, we can stay forever. 😆