Again, for everyone's convenience, a brief summary of our IRC meeting right here.
For greater details see meetbot
== Summary: ==
https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-...
== Full log: ==
https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-...
Topics discussed:
=== Follow up actions ===
DONE: Post on devel list thread F37 proposed change to GPT as default partitioning schema
about the regression regarding software raid installations.
DONE: Created an issue containing 2 test cases for biosboot GPT software raid
installations
https://pagure.io/fedora-server/issue/87
DONE: created a stub of NFS server installation and Cockpit for administration
ONGOING: Created Change proposal to add Server VM is still processing
ONGOING: Discussion about changes around the default hostname configuration
ONGOING: Review of the dnsmasq documentation by eseyman
=== Change proposal about GPT as default partitioning for bios boot ===
Discussion:
https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject....
FESCo has accepted the Change Proposal without discussion. We now have the problem of
preserving our users from harm unfortunately done intentionally or, at best, negligently
by some of our own members who are owners of the Change Proposal. Unfortunately, the
perpetrators do now not care how harm can be averted from our users with Release 37 and do
not even bother to attend the meeting on this topic to find a suitable resolution if the
issue.
Stephen Gallagher started a process to qualify the Anaconda software raid bug as a blocker
to the GPT Change Proposal. If accepted by QA as a blocker, it will have to be fixed (or
the Change reverted) in order to ship Fedora. This would be a perfect and constructive
solution.
Agreed: Server WG agrees with sgallagh’s suggestion to block the GPT change until the
Anaconda issue is resolved and considers it as most essential.
=== Planning for Fedora 37: Additional changes to discuss? (continued) ===
For part of the discussion we have a new tracking issue: #88. It summarizes all the
individual measures that we have discussed for improvement and entail an adjustment of the
installation media.
Agreed: Issue #88 is postponed to F38, due to current tasks and limited resources.
=== How to proceed with Cockpit File Sharing module NFS part ===
Due to the elapsed time further preparatory discussion via e-mail.