Meeting started at 2025-10-15 17:00:11 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.

!hello

Emmanuel Seyman (eseyman) - he / him / his

Hello, Peter

Hi Emmanuel, yeah, back again!

I will be coming and going in front of the computer during the meeting.

FTR, I am figuring out what to wear for a funeral tomorrow.

OK, Truly a bad reason, but truly one that cannot be postponed.

And a tricky problem nowadays.

!hi

Jocelyn Gould (korora) - she / her / hers

!hi

John Himpel (jwhimpel)

Welcome Jocelyn! It is good that you found the time.

Today has been.... much better than last week

!hi

Mat H (theprogram)

!hi

Jan Kuparinen (copperi)

Welcome MatH ! not only interested in Docs 😀

I have too many hats :)

Hm, Matrix tells my copperi is typing. Let's neverthless progress.

Any comments here?

I'm good

OK

One topic: in 14 days there is end of Daylight saving in Europe and in 3 weeks in US

So we have one week where our local times differ.

Last year it was always we European to cope with the change in daily routine.

And I guess, it is easier for us, because in is out of working time for us Europeans.

Should we proceed the same way this autumn?

+1

Emmanuel Seyman: ?? Vor me it's easy. For you?

I can cope with the change

!agreed: we switch to winter time in sync with US again.

zodbot: where are you?

Well, no zodbot / meetbot today.

Anything else here?

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

go/nogo meeting tomorrow.

Our SBC issuer is still not resolved, Minimal and Workstation the same.

So maybe, we have to put our decision to drop any SBC server image for F43 may be happen.

Any other news?

Obviously none.

At least we will be able to update the screenshots in our documentation. The rc doesn't carry the preview notice.

Maybe we have a short discussion in our Matrix room on Friday, the same time as now? (17:00 UTC)

I would change the order of topics and advance to the top 4

Because that's important when we update our docs.

objections?

OK.

proposal: https://hackmd.io/@pboy/BJnkUjA3el

Unfortunately, we had no discussion on Matrix last week.

Short break to read ?

Yes, please

OK. let me know if there are any access issues.

I signed in and have access

* Then we delete stg completely[...]

* In stg, we initially [...]

I'm not sure I understand the steps:

I feel like this proposal is good. It appears to follow the way that I understand git to be used

Emmanuel Seyman: the idea is to make a new stg strictly for those articles, we are discussing.

So we kind odf recreate stg with new content.

I'm not even sure we need stg even then, tbh

Yeah, we may have a good preview option in forgejo, soon. So, in the mean time stg may still a easy way to discuss.

Later it may be superfluous

In the meantime, your proposal works for me

I think am most fluent with docs current git flow, so I will do the modification in the next days.

On a somewhat related topic, will the ansible stuff in the old repo be automatically moved to the new repo? Or will manual migration be required?

The Ansible repo from pagure is already on forgejo without modifications, so far.

Picking up this opportunity: when will we be ready to continue our work on Ansible NFS. If I remember, Emmanuel Seyman and John Himpel had to do some work and wanted to coordinate efforts.

I did promise that...

So did I, but a new knee sort of become a higher priority.

Yeah, of course. I just don't want to give the impression that we're forgetting about it.

And, I already have the next “attack” up my sleeve. My text for standalone Samba is nearly complete.

I have to do some discussion with abbra , but otherwise ....

OK, lets continue with the agenda

Getting back to file servers sounds interesting I don't use Samba or NFS in my homelab, been happy with syncthing.

no Tracking issue

I'm on vacation this week, trying to spend time with my family (school holidays) and traveling.

abbra: Thanks for watching us nevertheless. I still need about 1 weekl to complete a first rough draft. And then no rush :-)

And enjoy undisturbed family life!

OK, how do we handle the pile of open issues?

proposal: each of us picks up one open issue and proposes what to do with it - or does the required action.

And next week we can discuss the progress we made.

So, each enters themself as "assigned" to mark the picked up issues

I'm assuming all these are on pagure?

currently both on pagure and forge.

We should use forge, i think.

Most of them are in pagure, though

Okay so we just focus on forge and consider pagure issues archived or something like that?

Emmanuel Seyman: "them" relates to issues or members?

them == issues

mowest: I think Peter had in mind that we would either close the issue or dupe it in forgejo (and then close it)

OK, I copies all issues from pagure to forge, so both are in sync.

As soon as docs has switched our docs to forge (I'm working on this, not that easy), I will close pagure.

oh, then close all pagure tickets. What point is there in keeping them open ?

oh, then close all pagure tickets. What point is there in keeping them open?

there is no point,

exactly

I suppose, the forge team has a plan what to do with pagure and how to do. I think, we should follow Fedora procedure, if there is any. I'll ask over there.

Anyway, I modify the README on pagure later today.

proposed !agreed Each WG member selects an open issue on Forge and either makes a suggestion on what to do or deals with the issue themselves until next week meeting.

objections?

works for me

Works for me

Next top

MatH: Happy to see you here. How can I persuade you to join us?

Hm, obviously he is off. It's a great cooperation with him in Docs.

OK, anything else here today?

So I'll close now.