<@pboy:fedora.im>
18:00:16
!startmeeting fedora-server
<@meetbot:fedora.im>
18:00:18
Meeting started at 2025-12-17 18:00:16 UTC
<@meetbot:fedora.im>
18:00:18
The Meeting name is 'fedora-server '
<@pboy:fedora.im>
18:00:23
!topic Roll Call
<@pboy:fedora.im>
18:00:34
!hi
<@zodbot:fedora.im>
18:00:36
Peter Boy (pboy)
<@eseyman:fedora.im>
18:00:45
!hello
<@zodbot:fedora.im>
18:00:46
Emmanuel Seyman (eseyman) - he / him / his
<@korora:fedora.im>
18:01:07
!hi
<@zodbot:fedora.im>
18:01:08
Jocelyn Gould (korora) - she / her / hers
<@pboy:fedora.im>
18:03:18
I learnt something earlier, hopefully I got it right :-)
<@pboy:fedora.im>
18:03:24
!info Present
<@pboy:fedora.im>
18:04:50
Hm, i hoped zodbot is smart enough to list the currently joined members. I would have to do that manuelly.
<@pboy:fedora.im>
18:05:16
OK, lets start.
<@pboy:fedora.im>
18:05:26
!topic Agenda
<@pboy:fedora.im>
18:05:35
!info Follow-up actions & announcements
<@pboy:fedora.im>
18:05:45
!info Status migration to forge.fedoraproject.org
<@pboy:fedora.im>
18:05:53
!info Restructuring the Server User Documentation
<@pboy:fedora.im>
18:06:01
!info Pending reviews of our documentation
<@pboy:fedora.im>
18:06:11
!info Our progam and working plan for the upcomming year
<@pboy:fedora.im>
18:06:20
!info Walk through longterm open issues and PRs
<@pboy:fedora.im>
18:06:28
!info Open Floor
<@pboy:fedora.im>
18:06:44
Anything to add / remove ?
<@eseyman:fedora.im>
18:06:55
I'm good
<@pboy:fedora.im>
18:07:01
OK Let's start
<@pboy:fedora.im>
18:07:10
!topic 1. Follow-up actions & announcements
<@pboy:fedora.im>
18:07:19
https://docs.fedoraproject.org/en-US/server-working-group/wg-minutes-2025/
<@pboy:fedora.im>
18:07:19
meetings overview:
<@pboy:fedora.im>
18:07:19
Regarding the action, I'll include the list in our
<@pboy:fedora.im>
18:07:44
Our planning for the next meeting.
<@pboy:fedora.im>
18:07:56
I suppose we cancel for Dec. 24 and Dec 31
<@pboy:fedora.im>
18:08:23
But I'm open if we want to meet 😀😏
<@korora:fedora.im>
18:08:36
Seconded on current proposal
<@pboy:fedora.im>
18:09:01
Yeah, Question is, should we start next year on Jan. 7 or Jan 14
<@korora:fedora.im>
18:09:37
I'm good with either]
<@pboy:fedora.im>
18:09:55
Me either
<@eseyman:fedora.im>
18:09:58
Agreed...
<@eseyman:fedora.im>
18:10:21
Let's go with 7th
<@pboy:fedora.im>
18:10:28
agreed.
<@pboy:fedora.im>
18:11:12
!agreed: Next meeting will be January 7, 2026
<@pboy:fedora.im>
18:11:48
Ok, zodbot sleeping again.
<@pboy:fedora.im>
18:12:07
!agreed Next meeting will be January 7, 2026
<@pboy:fedora.im>
18:12:53
w/o colon seems to work today. I'm lost, sometimes with sometimes w/o?
<@pboy:fedora.im>
18:13:02
Next topic:
<@pboy:fedora.im>
18:13:11
FESCo elecion is now open, until January 1
<@pboy:fedora.im>
18:13:22
https://elections.fedoraproject.org/about/f43-fesco
<@pboy:fedora.im>
18:13:32
7 candidates, 5 seats
<@pboy:fedora.im>
18:15:13
We had discussed once in a while that Server matters are sometimes not taken really serious. So, this election is not unimportant.
<@pboy:fedora.im>
18:16:13
And the last day, January 1, is maybe not the easiest choice. Hopefully everyone is back to normal after the end-of-year party.
<@eseyman:fedora.im>
18:17:31
And we still do not have a summary of the private discussion and vote FESCO had last year...
<@pboy:fedora.im>
18:18:33
We should do that, probably via mail.
<@pboy:fedora.im>
18:19:10
I think you refer to the proven packager status discussion?
<@pboy:fedora.im>
18:19:36
Anyway, we should continue this topic via mail.
<@pboy:fedora.im>
18:19:45
Last not least:
<@eseyman:fedora.im>
18:20:08
Yes
<@pboy:fedora.im>
18:20:33
CfP for Flock June 2026 is still open, but closing date is astonishinbgy early this year.
<@pboy:fedora.im>
18:20:54
Let's have a look
<@eseyman:fedora.im>
18:21:06
Yes, the day after FOSDEM
<@pboy:fedora.im>
18:22:00
Yes, CfP open until February 2
<@jflory7:fedora.im>
18:22:47
The last day to vote is January 7th, FWIW. I have a TODO to send a reminder mail to announce lists and Community Blog about voting
<@pboy:fedora.im>
18:24:46
The schedule says, January 1 (https://fedorapeople.org/groups/schedule/f-43/f-43-elections-tasks.html
<@pboy:fedora.im>
18:25:34
Hm, and I'm sure I've read Jan. 1, OK SORRY, it is January 7
<@pboy:fedora.im>
18:26:26
So, relax a little.
<@pboy:fedora.im>
18:27:20
But Feburary 2 is obviously correct.
<@korora:fedora.im>
18:27:50
You're talking about the Announce@fedoraproject.org list, correct?
<@eseyman:fedora.im>
18:28:52
announce and devel-announce, I would imagine
<@jflory7:fedora.im>
18:29:52
For the Flock CFP, yes!
<@pboy:fedora.im>
18:29:59
I don't remember where I found the link. It is on my list of most important links.
<@jflory7:fedora.im>
18:30:04
Yes, that's right. Both lists.
<@pboy:fedora.im>
18:30:48
Well, we need to consider if and what to contribute. It is about half a year before the event. And we might have not everything ready in February.
<@pboy:fedora.im>
18:31:47
We should start to discuss this on our first meeting in ernest. And on matrix beforehand.
<@eseyman:fedora.im>
18:32:01
Agreed
<@pboy:fedora.im>
18:32:09
Oh, ist late. lets proceed.
<@pboy:fedora.im>
18:32:18
!topic 2. Status migration to forge.fedoraproject.org
<@pboy:fedora.im>
18:32:29
!link https://forge.fedoraproject.org/server/tickets/issues/173
<@pboy:fedora.im>
18:32:39
max 10 mins.
<@pboy:fedora.im>
18:32:52
We agreed to continue consolidating all tickets in the tickets repro.
<@pboy:fedora.im>
18:33:03
Any additional idea / comment here? New experiences with the forge?
<@eseyman:fedora.im>
18:33:55
Mostly positive experience from my PoV
<@eseyman:fedora.im>
18:34:31
I do encourage WG members to assign issues and projects to themselves so that we can tell who is working on what
<@pboy:fedora.im>
18:35:02
Yeah, so no change so far.
<@pboy:fedora.im>
18:35:25
I mean, change of the repo structure.
<@pboy:fedora.im>
18:35:36
!topic 3. Restructuring the Server User Documentation
<@pboy:fedora.im>
18:35:45
!link https://forge.fedoraproject.org/server/tickets/issues/174#
<@pboy:fedora.im>
18:35:54
10 mins max.
<@pboy:fedora.im>
18:36:02
On a matrix discussion we were to remove the stg branch. I checked again, there are currently only Jocelyn's NFS additions and corrections and my postgresql update. Both are also available in a AsciiDoc preview in the forge.
<@pboy:fedora.im>
18:36:09
If we still agree, I would remove stg from the Docs build system together with other adjustments we are currently doing. And then remove it from forge.
<@eseyman:fedora.im>
18:36:19
Yes, please!
<@pboy:fedora.im>
18:36:20
Any other comment / idea / experiences
<@pboy:fedora.im>
18:36:39
Jocelyn (she/her) (Server WG: Docs): ??
<@korora:fedora.im>
18:36:58
I have nothing at this time
<@pboy:fedora.im>
18:37:12
OK
<@korora:fedora.im>
18:37:31
+1 to removing stg
<@pboy:fedora.im>
18:37:39
!agreed We will finally remove the stg branch from our Docs repo.
<@pboy:fedora.im>
18:37:55
!topic 4. Pending reviews of our documentation
<@pboy:fedora.im>
18:38:05
No tracking issue
<@pboy:fedora.im>
18:38:17
The Postgresql update is still open and needs a review.
<@pboy:fedora.im>
18:38:17
https://forge.fedoraproject.org/server/user-documentation/src/branch/stg/modules/ROOT/pages/services/postgresql-setup.adoc
<@pboy:fedora.im>
18:38:17
This is the link directly into the forge with a provisional formatting
<@pboy:fedora.im>
18:39:03
I think we don't have a chance for a review "this year" 😉
<@pboy:fedora.im>
18:39:13
roposal: Agreed: published with note about outstanding final review
<@pboy:fedora.im>
18:39:27
before it gets outdated because of F44
<@pboy:fedora.im>
18:39:59
Any objections?
<@eseyman:fedora.im>
18:40:46
No, let's publish it. We can fix any issues afterwards
<@pboy:fedora.im>
18:41:05
OK
<@korora:fedora.im>
18:41:14
No objections. (Perhaps we can discuss early in the year while we are still in the 44 cycle
<@copperi:fedora.im>
18:41:46
That looks ok to me
<@pboy:fedora.im>
18:42:33
Good, Jan welcome (for others, he helped us years ago to te
<@korora:fedora.im>
18:42:40
I can look at it, but I have little to know familiarity with Postgresql
<@pboy:fedora.im>
18:42:54
Good, Jan welcome (for others, he helped us years ago to get our docs up and running.
<@pboy:fedora.im>
18:43:47
Let's add copperi to the reviewer and lets publish as is.
<@pboy:fedora.im>
18:43:55
Any objections?
<@korora:fedora.im>
18:44:03
No objections
<@eseyman:fedora.im>
18:44:05
No
<@eseyman:fedora.im>
18:44:34
I will have a look over the document during my vacation
<@pboy:fedora.im>
18:44:48
Yes, any proofreading is welcome.
<@pboy:fedora.im>
18:45:30
!agreed We will publish the postgresql update now.
<@pboy:fedora.im>
18:45:41
!topic 5. Our program and working plan for the upcomming year
<@pboy:fedora.im>
18:45:51
Tracking ticket: https://forge.fedoraproject.org/server/tickets/issues/178
<@pboy:fedora.im>
18:46:02
These are the commitments and possible topics we got from the Matrix discussion.
<@pboy:fedora.im>
18:46:23
Is everybody OK with the summary so far?
<@korora:fedora.im>
18:47:12
Looks good to me
<@eseyman:fedora.im>
18:47:46
Yes
<@pboy:fedora.im>
18:48:03
I'm considering to develop a kind of extended rescue system. A minimal system with network access and booted by a watchdog, of supported by firmware.
<@pboy:fedora.im>
18:48:34
But I need to find a kernel / system export willing to help us.
<@pboy:fedora.im>
18:49:00
I'm considering to develop a kind of extended rescue system. A minimal system with network access and booted by a watchdog, if supported by firmware.
<@pboy:fedora.im>
18:50:15
OK, anyway, so far no objections. So we can finally decide next meeting and have some time to mull it over - and to make detailed implementation plans.
<@conan_kudo:matrix.org>
18:50:31
hmm, I've done something like that before
<@conan_kudo:matrix.org>
18:50:38
and even poked at the idea for fedora a few times
<@conan_kudo:matrix.org>
18:51:21
it's been on my list to look at again for at least desktop fedora, and server fedora is a subset of that
<@eseyman:fedora.im>
18:51:22
There is a system rescue group in comps, IIRC
<@pboy:fedora.im>
18:52:18
Conan Kudo: It was you I thought of :-)
<@conan_kudo:matrix.org>
18:52:40
I don't see it in f44 comps, it was present it must have been a long time ago
<@conan_kudo:matrix.org>
18:53:15
making a useful rescue environment has been part of the development plans in the fedora btrfs sig too
<@conan_kudo:matrix.org>
18:53:27
mostly because with btrfs we can do it in a way that doesn't take up too much extra space
<@pboy:fedora.im>
18:54:09
I think extra space is not an issue with server.
<@pboy:fedora.im>
18:54:45
We would probably need 2-4 gb for a server rescue partition, I suppose.
<@pboy:fedora.im>
18:55:00
For destop you need much more, I think
<@pboy:fedora.im>
18:55:37
Well, let's this discuss on matrix. I have one topic left, and we are nearly out of time!
<@pboy:fedora.im>
18:55:48
!topic 6. Walk through longterm open issues and PRs
<@pboy:fedora.im>
18:55:58
no Tracking issue
<@pboy:fedora.im>
18:56:12
7. Cockpit File Sharing module #86
<@pboy:fedora.im>
18:56:21
https://forge.fedoraproject.org/server/tickets/issues/86
<@pboy:fedora.im>
18:56:32
The new navigation module is available for some time
<@pboy:fedora.im>
18:56:40
Cockpit Files (by cockpit project) (rpm avialable)
<@pboy:fedora.im>
18:56:47
Do we want to make it installed by default or is this nothing for the hardcore admin and we leave it to postinstall?
<@pboy:fedora.im>
18:57:15
We didn't decide yet, because there was only the c46 solution.
<@eseyman:fedora.im>
18:57:23
security-lab: Tools for security auditing, forensics, system rescue, and teaching security testing methodologies.
<@conan_kudo:matrix.org>
18:57:45
ah that's not really for system rescue
<@pboy:fedora.im>
18:59:10
Yea, I think we need a minimal server system to fix filesystem issues and to install a previous snapshot. somehting like that.
<@pboy:fedora.im>
18:59:29
And we need to do it w/p access to server terminal.
<@pboy:fedora.im>
18:59:47
:-)
<@conan_kudo:matrix.org>
19:00:05
there's been discussions in #btrfs:fedoraproject.org about boot to snapshot too, for F45 possibly
<@conan_kudo:matrix.org>
19:00:27
so there's a lot of nice things that could line up and result in a drastic improvement in these scenarios
<@pboy:fedora.im>
19:01:02
Looking forward, but please, back to the current topic 😀
<@pboy:fedora.im>
19:01:19
(the other is much more ixciting, I know)
<@eseyman:fedora.im>
19:01:41
Don't really have an opinion here.
<@eseyman:fedora.im>
19:01:41
I suppose we can leave it to postinstall
<@pboy:fedora.im>
19:02:18
yeah, the hardcore admin 😊
<@pboy:fedora.im>
19:02:58
I agree, basically. In a homelab spin off we should install it by default.
<@pboy:fedora.im>
19:03:08
Jocelyn (she/her) (Server WG: Docs): ??
<@korora:fedora.im>
19:04:01
A minimal server image sounds like a good idea to me for recovery purposes
<@pboy:fedora.im>
19:04:43
Yes, and to you have an opinion about the navigator / files app for Cockpit?
<@korora:fedora.im>
19:05:31
It's something i'd like to see (I use cockpit for some things) but it's not something I use on a regular basis
<@pboy:fedora.im>
19:05:32
But maybe we should leave it for next meeting (again 😙 ), or Matrix.
<@pboy:fedora.im>
19:06:12
OK, our time is off. Let's consider it w/o a rush next meeting or on matrix.
<@pboy:fedora.im>
19:06:26
!topic 7. Open Floor
<@pboy:fedora.im>
19:06:43
Anything to add here?
<@korora:fedora.im>
19:07:30
I have nothing
<@pboy:fedora.im>
19:07:59
Ok, I'll close now
<@pboy:fedora.im>
19:08:08
!endmeeting