<@pboy:fedora.im>
17:00:08
!startmeeting fedora-server
<@meetbot:fedora.im>
17:00:09
Meeting started at 2025-09-10 17:00:08 UTC
<@meetbot:fedora.im>
17:00:10
The Meeting name is 'fedora-server'
<@pboy:fedora.im>
17:00:15
I'll post the agenda in 2-3 minutes.
<@pboy:fedora.im>
17:00:15
As usual, let's wait a moment for everybody to show up.
<@eseyman:fedora.im>
17:02:04
Hello, Peter Boy (ServerWG, Docs) !
<@eseyman:fedora.im>
17:02:06
!hello
<@zodbot:fedora.im>
17:02:08
Emmanuel Seyman (eseyman) - he / him / his
<@pboy:fedora.im>
17:02:34
Welcome Emmanuel!
<@pboy:fedora.im>
17:02:48
Thanks for writing to the tomcat folks!
<@eseyman:fedora.im>
17:03:20
I just got back from work and have read their reply.
<@pboy:fedora.im>
17:05:31
yeah I read that, too. Well, a case about "scope" and "assignment"
<@pboy:fedora.im>
17:06:09
And usually, a reverse proxy uses localhost, not really a "network" access.
<@pboy:fedora.im>
17:06:41
And the default configuration is using localhost, too
<@eseyman:fedora.im>
17:06:51
in this case, localhost is network access
<@pboy:fedora.im>
17:08:07
Yes, but no public access and no security thread
<@pboy:fedora.im>
17:08:29
Yes, but no public access and no security threat
<@eseyman:fedora.im>
17:09:57
Given that you're running a reverse proxy, "no public access" seems a bit of a stretch
<@pboy:fedora.im>
17:10:39
OK, yeah, but there is no direct public access to localhost.
<@pboy:fedora.im>
17:11:12
And is someone compromises the system, you may have more urgent issues as localhost. :-)
<@eseyman:fedora.im>
17:11:42
anyway, will reply later tonight
<@pboy:fedora.im>
17:12:56
OK, let's see here. We are just the two of us and nirik lurking as usual. I think, we short have a short look at the topcis, nevertheless.
<@eseyman:fedora.im>
17:13:22
Let's do that
<@pboy:fedora.im>
17:13:26
!topic Agenda
<@pboy:fedora.im>
17:13:35
!info Open Floor
<@pboy:fedora.im>
17:13:35
!info Follow-up actions & announcements
<@pboy:fedora.im>
17:13:35
!info Expansion to fedora server's release criteria
<@pboy:fedora.im>
17:13:35
!info Revision of Server SBC documentation
<@pboy:fedora.im>
17:13:35
!info F43 release testing
<@pboy:fedora.im>
17:13:35
!info Walk through longterm open issues and PRs
<@pboy:fedora.im>
17:13:53
!topic 1. Follow-up actions & announcements
<@pboy:fedora.im>
17:14:03
<@pboy:fedora.im>
17:14:03
!link https://docs.fedoraproject.org/en-US/server-working-group/wg-minutes-2025/
<@pboy:fedora.im>
17:14:03
Regarding the action, nothing new. See
<@pboy:fedora.im>
17:14:14
And no announcements from me.
<@pboy:fedora.im>
17:14:43
Anything else for the record?
<@eseyman:fedora.im>
17:14:50
No
<@pboy:fedora.im>
17:15:09
!topic 2. Expansion to fedora server's release criteria
<@pboy:fedora.im>
17:15:18
Tracking issue: !link https://pagure.io/fedora-server/issue/169
<@pboy:fedora.im>
17:15:56
At the moment there is nothing to do about this. But probably any questions?
<@pboy:fedora.im>
17:16:58
None, I see. So we are waiting for abbra 's proposal.
<@eseyman:fedora.im>
17:16:59
Nope
<@eseyman:fedora.im>
17:17:24
Yes, I trust abbra 's judgement here
<@abbra:matrix.org>
17:19:13
I need to make sure someone could do this work first. As Adam explained, there are some unsolved issues with the infra part. Once we are able to add the automation, we can expand the release criteria
<@pboy:fedora.im>
17:20:34
OK. How long cat we wait, or with other words, how essential is that?
<@pboy:fedora.im>
17:21:11
But we can deal with that when nothing is in sight for F44/45 yet.
<@pboy:fedora.im>
17:21:27
!topic 3. Revision of Server SBC documentation
<@pboy:fedora.im>
17:21:44
Traxking issue: !link https://pagure.io/fedora-server/issue/166
<@pboy:fedora.im>
17:21:52
!link https://docs.stg.fedoraproject.org/en-US/fedora-server/server-on-arm-sbc/
<@pboy:fedora.im>
17:22:57
Emmanuel Seyman: what's your first idea about that? You proposed some time ago to remove the SBC part from our main installation section.
<@pboy:fedora.im>
17:23:15
So it was originally your idea :-)
<@eseyman:fedora.im>
17:23:29
Did I?
<@pboy:fedora.im>
17:23:38
Yes!!!
<@pboy:fedora.im>
17:24:24
But you may have changed your mind in the meantime.
<@eseyman:fedora.im>
17:24:39
And I suspect the tracking issue is not that one
<@pboy:fedora.im>
17:24:47
oh
<@pboy:fedora.im>
17:25:47
It is https://pagure.io/fedora-server/issue/168
<@eseyman:fedora.im>
17:25:56
Much better
<@pboy:fedora.im>
17:26:11
yeah, copy&paste
<@eseyman:fedora.im>
17:26:42
My issue is that "SBC board" and "underpowered" are pretty much joined at the hip, in my mind
<@eseyman:fedora.im>
17:28:11
If CPU power is a concern, I suspect you're going to quickly disregard ARM SBC boards
<@pboy:fedora.im>
17:28:20
Yeah, but have a look at the new generation of Rockchip 3586 chips. They are not that much slower as an Intel n100 box. It's a big step forward.
<@pboy:fedora.im>
17:28:54
And you can use a "real" bios and Anconda install.
<@pboy:fedora.im>
17:29:41
But yes, there is a gap. So i think it is important, to draw a clear separation line.
<@eseyman:fedora.im>
17:31:32
but separating the "write to micro-SD card" and "do the actual install" use-cases seems a good idea
<@pboy:fedora.im>
17:33:39
We should/must emphasize that a suitable storage medium must be on board. The current Raspberry Pi 4 is a no-go.
<@pboy:fedora.im>
17:34:17
Well, what would be the alternative? Should we drop ARM SBC at all?
<@pboy:fedora.im>
17:35:02
We'll have a similiar question with the Risc V boards. I testet 2 of them (which currently the development boards of the SIG).
<@pboy:fedora.im>
17:36:15
They are generally better suited for server. But they are SBCs
<@eseyman:fedora.im>
17:36:47
I would hate to lose users simply because we don't want to maintain it
<@pboy:fedora.im>
17:37:53
So I take it as agreeing to follow the proposed path, basically. details to be discussed.?
<@eseyman:fedora.im>
17:38:10
Yes
<@pboy:fedora.im>
17:38:37
Regarding to lose users: Currently we can't F43 install at all. :-)
<@pboy:fedora.im>
17:39:12
So I'll finetune the text for a more intensive discussion later.
<@pboy:fedora.im>
17:39:30
So I'll finetune the text a bit for a more intensive discussion later.
<@pboy:fedora.im>
17:39:42
!topic 4. F43 release testing
<@pboy:fedora.im>
17:39:50
Tracking issue: !link https://pagure.io/fedora-server/issue/164
<@pboy:fedora.im>
17:40:33
The beta candidate is out today. On Thursday there is the go/no-go meeting.
<@pboy:fedora.im>
17:41:13
I started testing today with the SBC installation, which didn't work with the branched and rawhide version.
<@eseyman:fedora.im>
17:41:15
Still haven't found the time to test installation. Spent the weekend releasing security updates
<@pboy:fedora.im>
17:41:41
I still doesn't work: ee: https://bugzilla.redhat.com/show_bug.cgi?id=2391231
<@pboy:fedora.im>
17:42:31
Regarding testing: I'll be able to test our hardware installation part. Would be nice, if someone else could test the VM installations.
<@pboy:fedora.im>
17:43:27
In my previous test I didn't find a serious issue. That's why I'm optimistic.
<@eseyman:fedora.im>
17:43:58
That bug does look relatively easy to fix, if Peter R's comments are true
<@pboy:fedora.im>
17:44:50
Peter's provided an update to Arm tools, but it didn't fix the arm-installer-issue.
<@pboy:fedora.im>
17:45:22
And the ARM SIG is currently not in the best state.
<@eseyman:fedora.im>
17:45:50
I will try tomorrowx
<@eseyman:fedora.im>
17:45:56
I will try tomorrow
<@pboy:fedora.im>
17:46:04
👍️
<@pboy:fedora.im>
17:46:53
Maybe you can compare the F43 arm-image-installer with the F40 / F41 version. Those worked as far as I remember
<@pboy:fedora.im>
17:47:22
I don't know about F42. I think, we never tested that one.
<@eseyman:fedora.im>
17:47:54
Might as well try F41, F42 and F43 inthat order
<@eseyman:fedora.im>
17:48:01
Might as well try F41, F42 and F43 in that order
<@pboy:fedora.im>
17:48:19
Ok, yes. indeed the best way.
<@pboy:fedora.im>
17:49:20
Another issue is, the Beta does not include the minimal version. We need that for installation of devices with a soldered SPI module.
<@pboy:fedora.im>
17:49:48
It's really bad with the ARM devices this time.
<@pboy:fedora.im>
17:50:08
OK, let's proceed.
<@pboy:fedora.im>
17:50:18
!topic 5. Walk through longterm open issues and PRs
<@pboy:fedora.im>
17:50:48
I think we should skip again and wait for Paul Maconi (Aggraxis)
<@pboy:fedora.im>
17:51:03
And probably discuss in our Matrix room.
<@eseyman:fedora.im>
17:51:03
Let's
<@pboy:fedora.im>
17:51:09
OK.
<@eseyman:fedora.im>
17:51:15
I'm still hoping the new forge will help here
<@pboy:fedora.im>
17:51:27
topic 6. Open Floor
<@pboy:fedora.im>
17:51:38
Anything here?
<@pboy:fedora.im>
17:52:29
My question, we soon will have the switch to winter time.
<@eseyman:fedora.im>
17:52:46
any news on the PR against the httpd package?
<@pboy:fedora.im>
17:53:17
Can we follow the US timinn again? So we 2 have to change our daily routine for 2 meetings.
<@eseyman:fedora.im>
17:54:04
This would make the meeting earlier, then ?
<@pboy:fedora.im>
17:54:24
Regarding httpd: I have prepared the PR. I'm currentl looking into the build file for an opportunity to create the additional directory.
<@pboy:fedora.im>
17:54:54
Yeah, i suppose earlier, 1 hour.
<@pboy:fedora.im>
17:55:41
Back to httpd: When I made the PR, I'll sent a mail with the link.
<@eseyman:fedora.im>
17:56:13
I've had a few ideas since that I will email you about today or tomorrow
<@eseyman:fedora.im>
17:56:30
re US time : I can make it work
<@pboy:fedora.im>
17:56:57
OK, so I will adjust the Fedora calendar accordingly.
<@pboy:fedora.im>
17:57:10
And wait for the mail.
<@pboy:fedora.im>
17:57:29
Anything else?
<@eseyman:fedora.im>
17:59:14
No, I'm good
<@pboy:fedora.im>
17:59:15
Well, obviously not. Someone else lurking around with question or comment?
<@eseyman:fedora.im>
18:01:17
I think we're good (and I want to have dinner)
<@pboy:fedora.im>
18:01:27
OK
<@pboy:fedora.im>
18:01:36
!endmeeting