server August 2024

server@lists.fedoraproject.org

9 participants
17 discussions

2024-08-19 @ 16:00 UTC - Fedora 41 Blocker Review Meeting
by Adam Williamson 19 Aug '24

19 Aug '24

# F10 Blocker Review meeting # Date: 2024-08-19 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 41 blocker review meeting! We have 1 proposed blocker and 1 proposed freeze exception for Beta, and 6 proposed blockers 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 F40 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

1 0

Fedora on Raspberry Pi5 (sorta)
by John W. Himpel 14 Aug '24

14 Aug '24

I purchased an 8Gb model of the Raspberry Pi. I went to https://rpmfusion.org/Howto/RaspberryPi and downloaded the Server image for f40. Please note some non-Fedora software was included in the download. The list of copr's used in addition to the native Fedora f40 is show directly above the download tables. I used the Server image. I used balenaEtcher to flash the image onto an microSD card. Inserted the card into the Rpi5 and applied power. The boot is of course non-gui based. There are a couple of user interactions with anaconda, so you will need a keyboard and a monitor. All-in-all, it went extremely well. Initial testing shows the network functioning properly and storage is accessible. However, instead of using LVM ans xfs, this install created a btrfs volume with sub- volumes. Hope to find time in the next few days to explore this even more.

3 2

Agenda Items on 2024-08-14 17:00 ==UTC== meeting
by Peter Boy 14 Aug '24

14 Aug '24

The upcoming meeting will be held on ========================================================================== Fedora Server MATRIX meeting Wednesday, Aug 14 17:00 ==UTC== https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=cha… ========================================================================== Please, check your local time using date -d '2024-08-14 17: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. === 1. Follow up actions and announcements === === 2. Follow-up, findings and conclusions from Flock 2024 !link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or… About 30 mins max === 3. Ansible assisted installation and configuration of NFS service === !link https://pagure.io/fedora-server/issue/138 !link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or… !link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or… About 30 mins max === 4. Optimizing NFS service documentation === !link https://pagure.io/fedora-server/issue/138 !link https://docs.stg.fedoraproject.org/en-US/fedora-server/services/filesharing… === 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 ===== === Using Ansible to install and configure Wildfly !link https://pagure.io/fedora-server/issue/60 === Fedora Server in a virtualized runtime environment === link https://pagure.io/fedora-server/issue/110 === Revisiting Fedora Server quality criteria and procedures link https://pagure.io/fedora-server/issue/63 -- 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

1 0

[Fedocal] Reminder meeting : Fedora Server WG
by pboy＠fedoraproject.org 13 Aug '24

13 Aug '24

Dear all, You are kindly invited to the meeting: Fedora Server WG on 2024-08-14 from 17:00:00 to 18:00:00 UTC At not(a)irc.libera.chat The meeting will be about: Standing meeting of the Fedora Server Edition Working Group The meeting will be held on Matrix: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=cha… More information available at: [https://pagure.io/fedora-server/report/Meeting](https://pagure.io/fedora-se… Source: https://calendar.fedoraproject.org//meeting/10710/

2 1

[Fedocal] Reminder meeting : Fedora Server WG
by pboy＠fedoraproject.org 06 Aug '24

06 Aug '24

Dear all, You are kindly invited to the meeting: Fedora Server WG on 2024-08-07 from 17:00:00 to 18:00:00 UTC At not(a)irc.libera.chat The meeting will be about: Standing meeting of the Fedora Server Edition Working Group The meeting will be held on Matrix: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=cha… More information available at: [https://pagure.io/fedora-server/report/Meeting](https://pagure.io/fedora-se… Source: https://calendar.fedoraproject.org//meeting/10710/

2 1

fedora-server branches main vs stg are badly out of sync
by John W. Himpel 06 Aug '24

06 Aug '24

As I interpret Peter's last email, I should change my ansible roles into the "stg" branch. However the "main" branch has the fedora- ansible directory and associated subordinated content and the "stg" branch does not. Since I am a git neophite, should I commit the fedora-ansible directory in "stg" or should I hope someone with more git knowledge than myself sync the content between main and stg? I realize many of you are in-transit to Flock, so I will be patient waiting for a response and possible action on your part. John

1 0

What kind of workflow should we follow in Pagure?
by John W. Himpel 01 Aug '24

01 Aug '24

I'm obviously a newbie at Git and Pagure. But even a quick scan of the web soon leads to a decision point. What workflow model should be used. A cursory scan of the web suggests three possibilities: 1) GitFlow 2) GitHub Flow 3) GitLab Flow I don't know enough to even venture much of a guess as to which model we should follow. Another question enters my mind. Should the workflow for docs and the workflow for Ansible modules be the same? Or are there enough differences that each should have it's own separate workflow? Before I begin committing my Ansible Modules, I would like us to reach a consensus so that we don't have to make major workflow revisions later. Let the discussion begin!

3 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server August 2024