# F42 Blocker Review meeting
# Date: 2025-03-31
# Time: 16:00 UTC
# Location:
https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.…
Hi folks! It's time for a Fedora 42 blocker review meeting! We have 4
proposed blockers and 2 proposed freeze exceptions for Final.
Here is a handy link which should show you the meeting time
in your local time:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker…
The meeting will be on Matrix. Click the link above to join in a web
client - you can authenticate with your FAS account - or use a
dedicated client of your choosing.
If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F42 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good weekend and see you on Monday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
Hi folks! Sorry I missed the meeting last week. Just wanted to kick off
a mailing list topic for this. As briefly discussed at the meeting, the
aarch64 server netinst image is over its 'maximum size', and this is a
release-blocking bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2352679
we can either try and figure out why it got bigger and squish it back
down again, or just bump the policy maximum size. We're generally more
relaxed about maximum sizes these days since they're not so tied to
optical media any more and USB sticks are plentiful and cheap. The
current policy max is 1GB, and I don't remember the last time I saw a
1GB USB stick, so bumping to say 2GB probably wouldn't cause any
*practical* issues.
Still, it's nice to have these maximums so we catch any cases where
images are unnecessarily getting bigger. I do have a process for
figuring out what's taking up space on an image and I'll try to run
through that and post results on the bug later. These days, it
*usually* turns out to be linux-firmware getting bigger; various OEMs
are constantly dumping large blobs into linux-firmware these days,
something we can do little about :/
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
# F42 Blocker Review meeting
# Date: 2025-03-24
# Time: 16:00 UTC
# Location:
https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.…
Hi folks! It's time for a Fedora 42 blocker review meeting! We have 3
proposed blockers and 1 proposed freeze exception for Final.
Here is a handy link which should show you the meeting time
in your local time:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker…
The meeting will be on Matrix. Click the link above to join in a web
client - you can authenticate with your FAS account - or use a
dedicated client of your choosing.
If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F42 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good weekend and see you on Monday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
# F42 Blocker Review meeting
# Date: 2025-03-17
# Time: **16:00** UTC
# Location:
https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.…
Hi folks! It's time for a Fedora 42 blocker review meeting! We have 5
proposed blockers for Final.
Note that as clocks went forward in North America recently, the
meeting is now at 1600 UTC. If you changed your clocks recently,
the meeting will be at the same local time as before. If you didn't,
the meeting will be an hour earlier in your local time.
Here is a handy link which should show you the meeting time
in your local time:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker…
The meeting will be on Matrix. Click the link above to join in a web
client - you can authenticate with your FAS account - or use a
dedicated client of your choosing.
If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F42 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good weekend and see you on Monday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
The upcoming meeting will be held on
==========================================================================
Fedora Server MATRIX meeting Wednesday, Mar 12 18:00 ==UTC==
https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=cha…
==========================================================================
Please, check your local time using date -d '2025-03-12 18:00UTC'
==== Agenda ====
#link https://pagure.io/fedora-server/report/Meeting
To be able to discuss all topics on the agenda and to prevent us from repeatedly putting off topics that have not been dealt with, we should set time limits for the individual items on the agenda. If we need more time, we should continue on the mailing list.
To recap our discussion on last meeting see
https://docs.fedoraproject.org/en-US/server-working-group/wg-minutes-2024/
=== 1. Follow up actions and announcements ===
=== 2. Scheduled Server podcast for March 11
No tracking issue yet
The planned broadcast date had to be canceled. We now have the opportunity to plan further details.
=== 3. Cockpit self-signed certificates change
No tracking issue yet
link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or…
=== 4. How can we achieve progress with our Ansible Support
No tracking issue yet
Open discussion
=== 5. Open Floor
For any additions or changes, please reply to this email.
For an overview about current tasks look at:
https://pagure.io/fedora-server/boards/Works%20in%20progress
===== Pending Topics for Follow-Up Meetings =====
=== Fedora Server in a virtualized runtime environment ===
link https://pagure.io/fedora-server/issue/110
=== Future release testing procedures
!link https://pagure.io/fedora-server/issue/144
=== Revisiting Fedora Server quality criteria and procedures
link https://pagure.io/fedora-server/issue/63
=== Work program and goals
No Issue yet
=== Using Ansible to install and configure Wildfly
!link https://pagure.io/fedora-server/issue/60
=== Proposal: Fedora Server Edition - homelab spin-off
No tracking issue yet
Proposal draft
!link https://hackmd.io/@pboy/rJBhZYktye
—
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
Attention: Please don't respond to this mail, but to the GitHub discussion
mentioned below.
Hello all,
the Cockpit team is currently investigating a redesign of Cockpit's web server,
which becomes slowly but surely more pressing. See [1] for details if you are
interested. A very interesting possibility is to replace much of it with a web
service worker [2], which would allow us to make the architecture dramatically
simpler, more robust, and more secure (see prototype[3]).
The main concern with this approach is that web service workers don't work with
unknown TLS certificates ("secure context"), in particular for the self-signed
certificates that cockpit creates on startup if you didn't supply your own.
I. e. they don't support the usual TOFU model with "click here to accept this
unknown certificate anyway" that browsers show for "normal" web pages in this
case.
So I would like to do a little survey and request for comments about
deprecating or changing the handling of self-signed TLS certs in Cockpit. This
is an annoyingly hard problem: On one hand we really want to build a world
where TLS works and your services are trustworthy (*especially* if you are
typing in your root password as the next thing!), but for many home or even
small business situations even LetsEncrypt etc. is impractical/impossible (no
DNS, etc.). My questions:
* Are you currently accessing Cockpit with the builtin fallback self-signed
certificate?
* If so, would you have a better option like getting a proper cert, or joining
the machine to a FreeIPA domain (which requests a valid cert from the IPA
server), or running Cockpit behind a reverse proxy which already has a
proper certificate? Or using the Cockpit Client flatpak?
If any of these don't work for you, can you describe your situation?
* If the above isn't possible, could you live with running the cockpit web
server on a machine which has proper TLS setup, and connect to your target
machines with SSH?
* As last resort, Cockpit could show an error page (after accepting the
invalid certificate in the browser) which explains the situation and offers
you to download the CA certificate for importing into your browser as
trusted CA. This includes the case that the default self-signed certificate
is not valid for the hostname you are using to connect to cockpit (i.e. not
"localhost" or the server's unqualified host name) - then you need
to regenerate the certificate with the additional name.
This could then be used to actually establish some trust to the certificate,
by something like `ssh remote cockpit-show-cert` which would show you the
fingerprint or similar -- then you have something actually meaningful to
check in the browser.
Would that be acceptable for you?
* Are you working on a different web-based project and already have some experience
with handling proper certificates?
Notes:
* This only affects remote connections -- if you connect to your own machine
on http://localhost:9090, you can use unencrypted HTTP and service workers
are fine.
* We are aware of and use `sscg` if it's installed (cockpkit-ws.rpm
Recommends: it). We can change the non-sscg fallback to also create a
separate CA and cert, instead of the single self-signed cert. So that's not
a problem, just a bit of work.
Please respond on https://github.com/cockpit-project/cockpit/discussions/21695
to keep the responses in one place -- this annoucement goes to several mailing
lists.
Thank you!
Martin
[1] https://issues.redhat.com/projects/COCKPIT/issues/COCKPIT-1238
[2] https://developer.mozilla.org/de/docs/Web/API/Service_Worker_API
[3] https://issues.redhat.com/browse/COCKPIT-1240
# F42 Blocker Review meeting
# Date: 2025-03-10
# Time: **16:00** UTC
# Location:
https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.…
Hi folks! It's time for a Fedora 42 blocker review meeting! We have 4
proposed blockers and 3 proposed freeze exceptions for Beta, and 2
proposed blockers for Final.
Note that as clocks went forward in North America this weekend, the
meeting is now at 1600 UTC. If you changed your clocks this weekend,
the meeting will be at the same local time as before. If you didn't,
the meeting will be an hour earlier in your local time.
Here is a handy link which should show you the meeting time
in your local time:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker…
The meeting will be on Matrix. Click the link above to join in a web
client - you can authenticate with your FAS account - or use a
dedicated client of your choosing.
If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F42 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good weekend and see you on Monday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
# F42 Blocker Review meeting
# Date: 2025-03-03
# Time: 17:00 UTC
# Location:
https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.…
Hi folks! It's time for a Fedora 42 blocker review meeting! We have 2
proposed blockers and 4 proposed freeze exceptions for Beta, and 1
proposed blocker for Final.
Here is a handy link which should show you the meeting time
in your local time:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker…
The meeting will be on Matrix. Click the link above to join in a web
client - you can authenticate with your FAS account - or use a
dedicated client of your choosing.
If you have time today, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F42 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good day and see you tomorrow!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net