The upcoming meeting will be held on ========================================================================== Fedora Server MATRIX meeting Wednesday, Feb 21 18:00 ==UTC== https://matrix.to/#/#meeting:fedoraproject.org?web-instance%5Belement.io%5D=... ==========================================================================
Please, check your local time using date -d '2024-02-21 18:00UTC'
As a reminder ============= We decided to continue our meetings on MATRIX!
Unfortunately I couldn't manage to adjust the link in the automated reminder in time. So the link to IRC there is WRONG!
The above link lets you choose which app to use: web browser, elements, and a lot of others, including some CLI tools, and redirects you to the meeting romm.
If you don't have a Matrix account yet, the easiest way is to start at https://chat.fedoraproject.org. Using the option Create Account this page guides you perfectly through the required steps.
It you already use Matrix, you may have to add Fedora-meeting to your to your rooms list. Select Fedora space in the left most column in element oder web browser (not the Fedora room in the adjacent column). In the main opens a quite long list of Fedora rooms, but most importent a search field, where you can look for 'meeting'.
==== 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.
=== 1. Follow up actions and announcements ===
=== 2. LVM2 default configuration change #link https://bugzilla.redhat.com/show_bug.cgi?id=2258764 #link https://bugzilla.redhat.com/show_bug.cgi?id=2246871 #link https://bugzilla.redhat.com/show_bug.cgi?id=2247872
=== 3. Testing F40 === #link https://pagure.io/fedora-server/issue/125
We need to discuss - the current state of tests - evaluation of the change set regarding Server - How to continue moving away from hackmd
=== Revisiting Server installation media naming convention https://pagure.io/fedora-server/issue/126
=== 4. Our "story" for F40 https://pagure.io/fedora-server/issue/101
This includes a Server entry to the Release Notes!
=== 5. Work program and goals for F40/41 === Previous discussion: Fedora Server goal(s) for F39 #link https://pagure.io/fedora-server/issue/102
=== 7. 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 the next meetings =====
=== Revisiting Fedora Server release criteria #link https://pagure.io/fedora-server/issue/61
=== Using Ansible to install and configure Wildfly #link https://pagure.io/fedora-server/issue/60
=== Review installation media #link https://pagure.io/fedora-server/issue/88
=== F39 Work Project: Fedora Server on (ARM) SBC #link https://pagure.io/fedora-server/issue/108
-- Peter Boy https://fedoraproject.org/wiki/User:Pboy PBoy@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
The upcoming meeting will be held on ========================================================================== Fedora Server MATRIX meeting Wednesday, Feb 21 18:00 ==UTC== https://matrix.to/#/#meeting:fedoraproject.org?web-instance%5Belement.io%5D=... ==========================================================================
Please, check your local time using date -d '2024-02-21 18:00UTC'
As a reminder ============= We decided to continue our meetings on MATRIX! This will be our first meeting on Matrix. Let’s see how it works.
The above link lets you choose which app to use: web browser, elements, and a lot of others, including some CLI tools, and redirects you to the meeting romm.
=== Unfortunately I couldn't manage to adjust the link in the automated reminder in time. === === So the link to IRC in the automated invitation is WRONG! ===
If you don't have a Matrix account yet, the easiest way is to start at https://chat.fedoraproject.org. Using the option Create Account this page guides you perfectly through the required steps.
It you already use Matrix, you may have to add Fedora-meeting to your rooms list. Select Fedora space in the left most column in element oder web browser (not the Fedora room in the adjacent column). In the main section opens a quite long list of Fedora rooms, but most important a search field, where you can look for 'meeting'.
Due to recent opportunities a slight change here!
==== 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.
=== 1. Follow up actions and announcements === (about 5 mins max)
=== 2. Review installation media === (about 20 mins) #link https://pagure.io/fedora-server/issue/88
This is a long standing but urgent issue. Tomáš Hrčka (humaton) will join us for this.
=== 3. Revisiting Server installation media naming convention === (about 10 mins max) #link https://pagure.io/fedora-server/issue/126 https://pagure.io/fedora-server/issue/126
=== 4. LVM2 default configuration change === (about 5 mins max) #link https://bugzilla.redhat.com/show_bug.cgi?id=2258764 #link https://bugzilla.redhat.com/show_bug.cgi?id=2246871 #link https://bugzilla.redhat.com/show_bug.cgi?id=2247872
=== 5. Testing F40 === (about 10 mins max) #link https://pagure.io/fedora-server/issue/125
We need to discuss - the current state of tests - evaluation of the change set regarding Server - How to continue moving away from hackmd
=== 6. Our "story" for F40 === (about 10 mins max) https://pagure.io/fedora-server/issue/101
This includes a Server entry to the Release Notes.
=== 7. 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 the next meetings =====
=== Work program and goals for F40/41 === Previous discussion: Fedora Server goal(s) for F39 #link https://pagure.io/fedora-server/issue/102
=== Revisiting Fedora Server release criteria #link https://pagure.io/fedora-server/issue/61
=== Using Ansible to install and configure Wildfly #link https://pagure.io/fedora-server/issue/60
=== Review installation media #link https://pagure.io/fedora-server/issue/88
=== F39 Work Project: Fedora Server on (ARM) SBC #link https://pagure.io/fedora-server/issue/108
-- Peter Boy https://fedoraproject.org/wiki/User:Pboy PBoy@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
* Peter Boy [20/02/2024 14:21] :
We need to discuss
- the current state of tests
- evaluation of the change set regarding Server
For the record, I went through the list of Changes programmed for Fedora 40 and isolated the following as being of interest to us:
* Arm Minimal Image OS-Build * Fedora IoT Bootable Containers * ibus-anthy 1.5.16 * ibus 1.5.30 * IoT Simplified Provisioning * Deprecate_ntlm_in_cyrus_sasl * ROCm 6 Release * F40 MariaDB MySQL repackaging * Wifi MAC Randomization * Build Fedora IoT using rpm-ostree unified core * Build Fedora Cloud Edition Images Using Kiwi in Koji * Systemd Security Hardening * Java 21 * LLVM 18 * Podman 5 * Restructure Kubernetes Packages * PHP 8.3 * Ruby 3.3 * Haskell GHC 9.6 and Stackage LTS 22 * Golang 1.22 * PostgreSQL 16 * Enable IPv4 Addresses Conflict Detection by Default * 389 Directory Server 3.0.x
Regards, Emmanuel
server@lists.fedoraproject.org