desktop September 2026

desktop@lists.fedoraproject.org

3 participants
7 discussions

2026-09-28 @ 16:00 UTC - Fedora 45 Blocker Review Meeting
by Adam Williamson 27 Sep '26

27 Sep '26

# F45 Blocker Review meeting # Date: 2026-09-28 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 4 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+45+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 F45 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

2026-09-21 @ 16:00 UTC - Fedora 45 Blocker Review Meeting
by Adam Williamson 20 Sep '26

20 Sep '26

# F45 Blocker Review meeting # Date: 2026-09-21 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 6 proposed blockers and 4 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+45+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 F45 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

Sep 15 2026 Fedora Workstation working group meeting summary
by Matthias Clasen 16 Sep '26

16 Sep '26

Summary Release blockers and password managers and repository additions discussed via ticket reviews. Fedora 45 Blocker Status Crony timekeeping bugs confused Mutter frame scheduling. Blocker bug should be filed. Game Mode Ticket Review Game Mode inclusion debated. Ticket closed pending actual performance data. Adding OnePassword to Repositories OnePassword repository inclusion debated. Vote passed in favor. Decisions Needs Further Discussion Filing a blocker bug for crony issue The group discussed filing a blocker bug for a crony issue causing timekeeping shifts and frame scheduling freezes in the system. Aligned Closing the game mode ticket The participants agreed to close the game mode ticket and keep shipping game mode by default. Adding OnePassword to third-party repositories The working group voted in favor of adding OnePassword to the third-party repositories. Next steps [Matthias Clasen] File Crony Blocker: Submit a blocker ticket for the timekeeping conflict issue identified between Crony and M. [Neal Gompa (Conan Kudo)] Fix 007 Launch: Update all desktop sessions to ensure the 007 daemon launches correctly. [Neal Gompa (Conan Kudo)] Submit 007 Issue: Draft and submit an upstream issue regarding integration difficulties for the 007 service. [The group] Test Gnome 51: Perform testing on the final Gnome 51 release once it becomes available. [The group] Review 007 Integration: Revisit the status of the 007 integration during the next meeting. [The group] Write Release Article: Review the draft Gnome release notes to identify and share interesting highlights for the magazine post. [Neal Gompa (Conan Kudo)] Document Podman 6: Compile details regarding Podman 6 changes and potential container issues in the tracking ticket. [Allan Day] Organize Tickets: Consolidate related meeting tickets to reduce the current backlog. [Allan Day] Close Game Mode: Summarize the discussion points in the ticket and proceed with closing it. [Neal Gompa (Conan Kudo)] Process OnePassword Request: Verify the technical viability of the OnePassword repository and respond to the approval ticket. [The group] Contact: Message Adrian on Matrix next week to monitor the status of the 007 and crony issues. Details Fedora 45 Release Blocker Status: Allan Day checked the Fedora 45 release blocker list and noted no immediate blockers affecting the workstation team directly. Neal Gompa (Conan Kudo) stated that the installer cannot configure GNOME layouts in real time due to missing local-one components, secondary language support has a freeze exception, an IBUS crash update is pending, and a Podman bug lacks a current fix (00:00:38). Matthias Clasen and Neal Gompa (Conan Kudo) also highlighted an unresolved issue between Crony and Mutter, alongside a reboot and power-off failure in Workstation attributed to a Security-Enhanced Linux policy bug (00:04:20). Crony Timekeeping and Power Management Updates: Matthias Clasen explained a bug where Crony adjustments to Network Time Protocol timekeeping confuse timestamps used by Mutter for frame scheduling, sometimes causing Mutter to stop rendering frames entirely. Allan Day requested a blocker bug be filed for this issue, and Matthias Clasen agreed to track it down (00:05:40) (00:08:26). Additionally, Neal Gompa (Conan Kudo) reported that *they* landed a batch of power and thermal management fixes for Intel-based laptops into the repositories, noting that thermal and power daemon packages like thermal-daemon and LPMD had not received updates in three to four years because the former maintainer, Benjamin Berg, left Red Hat (00:07:09). 007 Desktop Session Integration and GNOME Keyring Retirement: Neal Gompa (Conan Kudo) explained that the Fedora 45 beta was released with a broken 007 password manager daemon because upstream dropped D-Bus activation between the 0.6 and 0.7 alpha versions (00:09:53) (00:14:32). Neal Gompa (Conan Kudo) committed to rolling through other desktop sessions this week to fix 007 launching, while stating *they* are deferring the KDE Wallet to 007 migration to the next cycle due to time constraints (00:11:46). Neal Gompa (Conan Kudo) noted that GNOME Keyring is expected to be retired within one or two cycles (by GNOME 51 or 52), making the 007 integration mandatory (00:13:36). Allan Day and Matthias Clasen suggested organizing testing for the 007 implementation once GNOME 51 final is released and Neal Gompa (Conan Kudo) finishes integrating other desktop sessions (00:16:26). Beta Website Issues and Fedora Magazine Article: Neal Gompa (Conan Kudo) reported that the beta download links were temporarily unavailable because someone forgot to flip the website and FTP servers live when publishing magazine announcements (00:18:18). Allan Day brought up the pending Fedora Magazine article for the release, noting that finding distinct Fedora-specific highlights outside of GNOME release notes is difficult, and suggested using artificial intelligence to generate a draft from the existing GNOME release notes. Neal Gompa (Conan Kudo) added that Podman 6 should be mentioned with a warning because it lacks an automatic migrator and will likely break existing containers and toolboxes upon upgrade, offering to drop details into the ticket (00:19:35) (00:23:00). Game Mode Ticket Review: Michael Catanzaro brought up a ticket questioning the inclusion of Game Mode, a service preloaded on Workstation and KDE that automatically prioritizes foreground video game processes (00:26:02). Neal Gompa (Conan Kudo) defended Game Mode, stating *they* believe it provides a measurable impact for resource-intensive AAA titles and integrates into the software stack (00:26:59). Matthias Clasen questioned whether Game Mode makes a significant difference nowadays and noted overlaps with power modes, while highlighting a broader lack of a coherent Linux strategy for power and resource management daemons (00:28:12). Allan Day concluded the discussion by offering to summarize these points, close the ticket, and remain open to reopening it if actual performance data is provided (00:30:08). Adding OnePassword to Third-Party Repositories: Allan Day introduced ticket 529 requesting the addition of OnePassword to the third-party repositories via an official RPM repository and Flatpak remote (00:31:13). Michael Catanzaro strongly opposed adding random proprietary software repositories, arguing that open source alternatives like KeePassXC, VaultWarden, and RBW are already available and that the team should reduce third-party repositories rather than expand them (00:35:50). Conversely, Neal Gompa (Conan Kudo) advocated for inclusion, arguing that OnePassword dominates enterprise and developer environments, and pointing out that the RPM repository provides the command line utility necessary for developer automation and workflow integration (00:34:36) (00:42:03). Allan Day conducted a vote, resulting in four votes in favor, and Neal Gompa (Conan Kudo) volunteered to respond to the ticket and check technical requirements with OnePassword (00:40:31) (00:46:29). Upcoming Meeting Schedule and Absences: Matthias Clasen announced that *they* will be on vacation next week, and Neal Gompa (Conan Kudo) stated *they* will be traveling to Boston for DevCon US and later to Toronto for XDC (00:47:38). The participants discussed tracking remaining Fedora 45 blockers, such as the 007 integration and Crony issue, with Allan Day suggesting reaching out to Adrian on Matrix for updates during the upcoming absences (00:48:47).

1 0

2026-09-14 @ 16:00 UTC - Fedora 45 Blocker Review Meeting
by Adam Williamson 13 Sep '26

13 Sep '26

# F45 Blocker Review meeting # Date: 2026-09-14 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 1 proposed blocker and 4 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+45+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 F45 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

Sep 8th 2026 Fedora Workstation working group meeting summary
by Matthias Clasen 10 Sep '26

10 Sep '26

Summary Release updates and Flatpak strategies via discussions on blockers and metadata. Fedora Release Status Discussion on Fedora release blocking and offline update issues. Flathub Strategy and Outreach Exploration of Flatpak pre installation and diplomatic outreach plans. Decisions Aligned Strategy for FlatHub engagement defined The group decided to postpone the FlatHub discussion until Matthias completes fact-finding regarding available metadata, at which point the group will reconvene and potentially reinvite Jeff. Next steps [Allan Day] Ping blockers: Notify internal teams about the time sensitive release blocker for the Fedora 45 and 51 release candidate. Ensure stakeholders are aware of the current situation. [Allan Day] Update talking points: Include a link to the release notes in the Fedora 45 talking points tracking issue. Provide relevant documentation for the upcoming release. [Allan Day] Find article author: Search for a volunteer to write an article about the latest Fedora release. Utilize Matrix channels to identify interested authors. [Matthias Clasen] Investigate flatpack pre-installation: Investigate the current status of flatpack pre-installation support. Identify all missing requirements needed for implementation. [Matthias Clasen] Contact FlatHub developers: Initiate communication with FlatHub developers to discuss metadata availability. Assess the feasibility of collaborating on metadata standards. [Allan Day] Review Bazar app: Review the Bazar application regarding potential improvements for the Standard Technology Fund funded work. Examine the app for better usability and integration. [Matthias Clasen] Publish meeting notes: Compile and publish the notes for this meeting once the transcript email is received. Distribute the summary to the relevant team members. Details Opening and Meeting Status: Allan Day opened the meeting and checked on attendance, noting that the group was smaller than usual. Jiri Prajzner inquired about the installation of the web project featuring integrated speech-to-text, noting that they were unable to find installable packages within the latest daily Ubuntu ISO (00:00:37). Fedora 45 Release - 51 Release Candidate Status: Allan Day and the group discussed the current status of the Fedora 45 release, focusing on the blocking of the 51 Release Candidate (RC) for the beta. Matthias Clasen and Michael Catanzaro noted that while a freeze exception was accepted for 51 RC, it currently breaks open QA tests due to a Mutter bug (00:03:50). Matthias Clasen reported that Adam Williamson has been bisecting the issue, and the team is currently waiting for the relevant packages to be packaged before proceeding (00:05:20). Allan Day plans to internally ping relevant stakeholders to emphasize the time-sensitive nature of these issues (00:06:52). Fedora 44 Offline Update Issues: Michael Catanzaro reported that users have complained about broken offline updates in Fedora 44 when attempting to shut down the Gnome shell, an issue attributed to the recent transition from PackageKit to using DNF directly. Michael Catanzaro noted that developers, including Milan, are aware of the issue, and while the team acknowledged the inconvenience of this being the second occurrence this year, no direct action is required from the group at this time (00:08:34). Gnome 50 Release Planning and Marketing: Matthias Clasen noted that the Gnome 50 release is expected by the 16th. Allan Day mentioned having reviewed the release notes, describing them as positive with many small improvements, and suggested that marketing material could be developed based on these notes (00:10:02). The group discussed the need for an author to write about the release, as past protocols involving Fedora Magazine contributors are currently inactive (00:11:45). Matthias Clasen and Allan Day considered potential ways to identify new features, including utilizing AI to research kernel and systemd changes, though they acknowledged the need to verify any information generated (00:13:17). Allan Day committed to researching the release highlights and asking for a volunteer to write the article (00:15:15). Flathub Strategy and Pre-installation: The group continued the previous week's discussion regarding Flathub, emphasizing the need to find a sustainable path forward that aligns with the Fedora community's expectations (00:19:27) (00:25:30). Michael Catanzaro noted there is an existing, unapproved ticket regarding the pre-installation of Flatpaks, though they expressed skepticism about the project's current priority within Red Hat (00:21:12). Matthias Clasen offered to investigate the status of the technical building blocks required for pre-installation, as some work in this area by Sebastian has already been initiated (00:22:56). Michael Catanzaro outlined three tracks for the Flatpak strategy: curtailing Fedora Flatpaks, enabling Flathub, and pre-installing core Flatpak applications (00:24:15). Flathub Outreach and Metadata: Regarding the goal of modifying Flathub, Matthias Clasen, Allan Day, and Michael Catanzaro agreed that the approach should be diplomatic, positioning the discussion as a collaboration to make Flathub more successful rather than issuing demands (00:27:14) (00:29:53). Matthias Clasen committed to performing fact-finding on currently available Flathub metadata to inform these discussions (00:31:06). Jiri Prajzner confirmed that the Flatpak command currently queries remotes and suggested that extending this search functionality could address metadata requirements, such as licenses and application types (00:32:30). The group plans to reconvene in a few weeks to discuss the outreach progress and potentially re-invite Jef to the conversation (00:31:06). Future UX Work: Matthias Clasen acknowledged that there are various smaller and larger UX annoyances regarding the interaction with Flathub, such as end-of-life questions and renaming application IDs (00:33:53). Allan Day noted that upcoming work funded by the STF is expected to address some of these scrutiny and review aspects, and they intend to review the application and progress during future meetings (00:35:58).

2 1

2026-09-07 @ 16:00 UTC - Fedora 45 Blocker Review Meeting
by Adam Williamson 06 Sep '26

06 Sep '26

# F45 Blocker Review meeting # Date: 2026-09-07 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 2 proposed blockers and 7 proposed freeze exceptions for Beta. 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+45+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 F45 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! I may not see you tomorrow as I'll be on vacation, but somebody will be there to run the meeting. [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

Sep 1st 2026 Fedora Workstation WG Meeting Summary
by Matthias Clasen 01 Sep '26

01 Sep '26

Summary Strategic discussions regarding Flatpak metadata management and status updates on the Fedora 46 release were covered. Flatpak Strategy and Metadata Technical mechanisms for certifying third-party applications were evaluated against metadata maintenance burdens. The group aligned on a strategy to document policy requirements for upstream partners. Fedora 46 Release Update The release process reached beta freeze with testing showing expected results for GNOME 51. External hardware issues were identified but remain outside the scope of current release controls. Technical Blockers and Debugging Critical blockers regarding user switching failures and compositor instability were reviewed. Investigating authentication module support and kernel-level rendering issues remains a priority. Decisions Needs Further Discussion Metadata certification strategy deferral The group decided to defer the evaluation of a custom metadata certification process for FlatHub packages to the issue tracker for further investigation and future deliberation. Next steps [Jef Spaleta] Contact Debian: Reach out to Debian representatives to discuss the FlatHub certification strategy. [Matthias Clasen] Contact FlatHub: Discuss the certification proposal with FlatHub developers to explore potential collaboration. [Lee Thomas Stephen] Research Onboarding: Investigate the existing FlatHub review and onboarding documentation. [Matthias Clasen] Consult Adrian: Inquire about the user switching bug to determine if a fix is planned. [Matthias Clasen] Request PAM Clarification: Ask Adrian for details on how to enable Gnome Keyring PAM support. [Allan Day] Post Packaging Info: Share the name of the packaging lead in the Matrix room. [Jiri Prajzner] Review Ubuntu Speech: Test the Ubuntu speech-to-text integration and report impressions at the next meeting. Details Meeting Housekeeping: Matthias Clasen was confirmed as the official secretary for the meeting (00:02:32). Attendees included Allan Day, Matthias Clasen, Jef Spaleta, Michael Catanzaro, Neal Gompa (Conan Kudo), Lee Thomas Stephen, and Jiri Prajzner (00:01:36) (00:29:48). Flatpak Strategy and Metadata Certification: Jef Spaleta proposed a technical mechanism to allow third-party organizations, such as Fedora or openSUSE, to certify specific Flatpak content on FlatHub. This would create a subset of applications verified to meet organizational requirements without imposing policies on FlatHub itself. Matthias Clasen noted that previous discussions regarding filtering implementations raised concerns about the maintenance of metadata and the ability to perform emergency cut-offs if necessary (00:02:32). Technical Challenges of Metadata Management: Michael Catanzaro expressed concerns regarding the complexity and sustainability of maintaining separate metadata, suggesting that it would be a significant burden to keep such information up to date. Michael Catanzaro suggested this approach should be considered a fallback rather than a primary goal. Jef Spaleta clarified that this was an initial discussion intended to gauge potential alignment among various distributions (00:06:15). Defining Fedora's Requirements: Allan Day queried what specific criteria Fedora would use for such filters, referencing the need to define "open" and "rebuildable." Jef Spaleta emphasized that the intent was to allow organizations to define their own certification standards rather than prescribing them to FlatHub. Matthias Clasen noted that existing metadata, such as that provided by GitHub or FlatHub, could potentially serve as a basis for these policies (00:08:47). Sustainability and FlatHub Collaboration: Michael Catanzaro argued that relying on contributors to maintain metadata for 95% of packages was likely unrealistic and expressed skepticism regarding FlatHub developers' willingness to accommodate distribution requirements. Jef Spaleta stated an intent to consult with Debian representatives to determine if there is a shared perspective among distributions regarding their partnership with FlatHub (00:12:00). Addressing Communication Barriers: Jef Spaleta discussed the difficulty of the current "fence line" dynamic between distributions and FlatHub, aiming to find a way to communicate Fedora's policy requirements to users without creating conflict. Allan Day suggested that the path of least resistance might be for Fedora contributors to volunteer directly on FlatHub to ensure reviews meet Fedora's necessary standards (00:16:09). Collaboration Strategy and Diplomacy: Michael Catanzaro and Matthias Clasen expressed frustration with previous diplomatic attempts to collaborate with FlatHub developers. Allan Day suggested that providing a clear roadmap or defined requirements might motivate contributors to act. Jef Spaleta reiterated a commitment to finding a way to voice Fedora's requirements, expressing hope that such transparency might eventually influence upstream developers to meet those standards (00:18:48). Alignment on Policy Roadmap: Michael Catanzaro referenced a previously shared list of requirements, which included building from source and monitoring bundle dependencies, as a starting point. Jef Spaleta and Allan Day agreed that they are not out of alignment on the end goal, but rather seeking a workable path to communicate these needs. Allan Day suggested documenting these steps in the issue tracker (00:24:17). Matthias Clasen volunteered to contact FlatHub representatives to explore collaboration opportunities. Sep 1, 2026 Fedora Workstation Working Group meeting Invited Michael Catanzaro Matthias Clasen Nieves Montero Fernandez Allan Day Jef Spaleta Jens-Ulrik Petersen Tomáš Popela Owen Taylor Attachments Fedora Workstation Working Group meeting Notes - Fedora Workstation Working Group meeting Meeting records Transcript Summary Strategic discussions regarding Flatpak metadata management and status updates on the Fedora 46 release were covered. Flatpak Strategy and Metadata Technical mechanisms for certifying third-party applications were evaluated against metadata maintenance burdens. The group aligned on a strategy to document policy requirements for upstream partners. Fedora 46 Release Update The release process reached beta freeze with testing showing expected results for GNOME 51. External hardware issues were identified but remain outside the scope of current release controls. Technical Blockers and Debugging Critical blockers regarding user switching failures and compositor instability were reviewed. Investigating authentication module support and kernel-level rendering issues remains a priority. Decisions Needs Further Discussion Metadata certification strategy deferral The group decided to defer the evaluation of a custom metadata certification process for FlatHub packages to the issue tracker for further investigation and future deliberation. Next steps [Jef Spaleta] Contact Debian: Reach out to Debian representatives to discuss the FlatHub certification strategy. [Matthias Clasen] Contact FlatHub: Discuss the certification proposal with FlatHub developers to explore potential collaboration. [Lee Thomas Stephen] Research Onboarding: Investigate the existing FlatHub review and onboarding documentation. [Matthias Clasen] Consult Adrian: Inquire about the user switching bug to determine if a fix is planned. [Matthias Clasen] Request PAM Clarification: Ask Adrian for details on how to enable Gnome Keyring PAM support. [Allan Day] Post Packaging Info: Share the name of the packaging lead in the Matrix tunnel. [Jiri Prajzner] Review Ubuntu Speech: Test the Ubuntu speech-to-text integration and report impressions at the next meeting. Details Meeting Housekeeping: Matthias Clasen was confirmed as the official secretary for the meeting (00:02:32). Attendees included Allan Day, Matthias Clasen, Jef Spaleta, Michael Catanzaro, Neal Gompa (Conan Kudo), Lee Thomas Stephen, and Jiri Prajzner (00:01:36) (00:29:48). Flatpak Strategy and Metadata Certification: Jef Spaleta proposed a technical mechanism to allow third-party organizations, such as Fedora or openSUSE, to certify specific Flatpak content on FlatHub. This would create a subset of applications verified to meet organizational requirements without imposing policies on FlatHub itself. Matthias Clasen noted that previous discussions regarding filtering implementations raised concerns about the maintenance of metadata and the ability to perform emergency cut-offs if necessary (00:02:32). Technical Challenges of Metadata Management: Michael Catanzaro expressed concerns regarding the complexity and sustainability of maintaining separate metadata, suggesting that it would be a significant burden to keep such information up to date. Michael Catanzaro suggested this approach should be considered a fallback rather than a primary goal. Jef Spaleta clarified that this was an initial discussion intended to gauge potential alignment among various distributions (00:06:15). Defining Fedora's Requirements: Allan Day queried what specific criteria Fedora would use for such filters, referencing the need to define "open" and "rebuildable." Jef Spaleta emphasized that the intent was to allow organizations to define their own certification standards rather than prescribing them to FlatHub. Matthias Clasen noted that existing metadata, such as that provided by GitHub or FlatHub, could potentially serve as a basis for these policies (00:08:47). Sustainability and FlatHub Collaboration: Michael Catanzaro argued that relying on contributors to maintain metadata for 95% of packages was likely unrealistic and expressed skepticism regarding FlatHub developers' willingness to accommodate distribution requirements. Jef Spaleta stated an intent to consult with Debian representatives to determine if there is a shared perspective among distributions regarding their partnership with FlatHub (00:12:00). Addressing Communication Barriers: Jef Spaleta discussed the difficulty of the current "fence line" dynamic between distributions and FlatHub, aiming to find a way to communicate Fedora's policy requirements to users without creating conflict. Allan Day suggested that the path of least resistance might be for Fedora contributors to volunteer directly on FlatHub to ensure reviews meet Fedora's necessary standards (00:16:09). Collaboration Strategy and Diplomacy: Michael Catanzaro and Matthias Clasen expressed frustration with previous diplomatic attempts to collaborate with FlatHub developers. Allan Day suggested that providing a clear roadmap or defined requirements might motivate contributors to act. Jef Spaleta reiterated a commitment to finding a way to voice Fedora's requirements, expressing hope that such transparency might eventually influence upstream developers to meet those standards (00:18:48). Alignment on Policy Roadmap: Michael Catanzaro referenced a previously shared list of requirements, which included building from source and monitoring bundle dependencies, as a starting point. Jef Spaleta and Allan Day agreed that they are not out of alignment on the end goal, but rather seeking a workable path to communicate these needs. Allan Day suggested documenting these steps in the issue tracker (00:24:17). Engaging Interns and Onboarding: Matthias Clasen volunteered to contact FlatHub representatives to explore collaboration opportunities. Lee Thomas Stephen suggested that interns could be tasked with initial work and reviews. Neal Gompa (Conan Kudo) and Allan Day discussed the value of using interns to teach provenance and review processes. Allan Day tasked Lee Thomas Stephen with investigating the current onboarding and review processes on the FlatHub side (00:28:14). Fedora 46 Release Status: Allan Day provided an update on the Fedora 46 release, noting that the team is in the beta freeze phase with the beta release expected in a few weeks. Neal Gompa (Conan Kudo) reported that GNOME 51 test results were standard, with only minor, expected failures related to NVIDIA hardware. The team noted that issues with Anaconda and KMS Con are currently outside their control (00:32:24). GNOME Session User Switching: Allan Day and Neal Gompa (Conan Kudo) discussed a "fast user switching" failure listed as a final blocker. Matthias Clasen indicated this might be due to inhibitors preventing restarts. Matthias Clasen committed to following up with Adrian to address this matter (00:35:19). GNOME Keyring PAM Enablement: Neal Gompa (Conan Kudo) reported difficulty in identifying how the GNOME Keyring PAM support is enabled, as there was no clear documentation or spec file flag found. Michael Catanzaro suggested contacting the authselect developers for assistance. The participants agreed that documenting the solution upon discovery would be beneficial (00:36:34). Compositor Issues on Rawhide: Matthias Clasen reported a recurring issue on Rawhide where the compositor stops rendering, typically after a system suspend event. Matthias Clasen theorized this could be linked to clock synchronization or time-stamp adjustments during suspend, while Neal Gompa (Conan Kudo) suggested it might be a kernel issue. Allan Day asked for an update on the release candidate schedule and noted that while packaging is handled by Milan and Adrian, they likely cannot resolve this specific bug (00:39:44). Ubuntu Speech-to-Text Update: Jiri Prajzner mentioned that Ubuntu released a new speech-to-text feature. Jiri Prajzner agreed to test it and provide impressions at the next meeting, which Allan Day added to the agenda (00:43:56). Lee Thomas Stephen suggested that interns could be tasked with initial work and reviews. Neal Gompa (Conan Kudo) and Allan Day discussed the value of using interns to teach provenance and review processes. Allan Day tasked Lee Thomas Stephen with investigating the current onboarding and review processes on the FlatHub side (00:28:14). Fedora 46 Release Status: Allan Day provided an update on the Fedora 46 release, noting that the team is in the beta freeze phase with the beta release expected in a few weeks. Neal Gompa (Conan Kudo) reported that GNOME 51 test results were standard, with only minor, expected failures related to NVIDIA hardware. The team noted that issues with Anaconda and KMS Con are currently outside their control (00:32:24). GNOME Session User Switching: Allan Day and Neal Gompa (Conan Kudo) discussed a "fast user switching" failure listed as a final blocker. Matthias Clasen indicated this might be due to inhibitors preventing restarts. Matthias Clasen committed to following up with Adrian to address this matter (00:35:19). GNOME Keyring PAM Enablement: Neal Gompa (Conan Kudo) reported difficulty in identifying how the GNOME Keyring PAM support is enabled, as there was no clear documentation or spec file flag found. Michael Catanzaro suggested contacting the authselect developers for assistance. The participants agreed that documenting the solution upon discovery would be beneficial (00:36:34). Compositor Issues on Rawhide: Matthias Clasen reported a recurring issue on Rawhide where the compositor stops rendering, typically after a system suspend event. Matthias Clasen theorized this could be linked to clock synchronization or time-stamp adjustments during suspend, while Neal Gompa (Conan Kudo) suggested it might be a kernel issue. Allan Day asked for an update on the release candidate schedule and noted that while packaging is handled by Milan and Adrian, they likely cannot resolve this specific bug (00:39:44). Ubuntu Speech-to-Text Update: Jiri Prajzner mentioned that Ubuntu released a new speech-to-text feature. Jiri Prajzner agreed to test it and provide impressions at the next meeting, which Allan Day added to the agenda (00:43:56).

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop September 2026