Greetings testers! It’s meeting time again. Remember that clocks went back recently in places that observe daylight savings, so the meeting time is now 16:00 UTC. If you observe daylight savings, the meeting should be at the same time as usual. If you do not, it is one hour later than it was over summer.
Here is an AI-generated summary of a Fedora Quality meeting from 2025-12-08.
Please be aware that the summary is intended for a quick convenient recapitulation of the meeting, but might contain factual errors. Read the full meeting log for all the details.
Previous Meeting Follow-up
The follow-up item regarding filing an issue to draft a note to mesa maintainers about the update situation was considered resolved, as the involved maintainers were already active in the Discourse threads, making the ticket unnecessary.
Fedora CI pull requests and openQA tests have been created related to the mesa layer issue:
Fedora CI: Petr Sklenar created a PR to enable Fedora CI for mesa.
openQA: Adam Williamson created written tests for the mesa layer issue at both the openQA level and the package level.
Fedora 44 Status
Lukáš Růžička proposed a Basic Networking test case, which can be reviewed on the Fedora Wiki. The test case was noted for its good coverage but considerable length, with Lukáš intending to convert it into an openQA test.
Kamil Páral suggested that while openQA tests and wiki tests don’t need a 1:1 mapping, all release criteria should be covered by wiki tests. Kamil expressed a preference for the openQA test to be more complex and automated, while the wiki test should be simpler and tailored toward human testers, focusing on testing their default network configuration rather than complex static setups. Lukáš explained the complexity and length arose from trying to provide a robust setup for testing IPv6 when a tester’s default environment might not support it. He agreed to simplify the test for common human scenarios.
Incident Report Process Proposal
The discussion focused on a proposal for an Incident Report Process and whether it should be a new Special Interest Group (SIG) or be integrated into the existing Quality Assurance (QA) team.
Group Affiliation: It was agreed that the process makes sense as a part of the QA team instead of a new SIG, especially since initial community feedback for a new SIG was limited.
Karma and Updates: There was support for making the karma system a little more strict, with Adam noting that a single negative karma currently disables autopush (which the maintainer can override), and a default of -3 karma unpushes an update. A need for better visibility of negative karma, such as posting them to the #quality:fedoraproject.org channel, was suggested.
Process Implementation: Adam suggested doing the whole process through the Fedora Discussion forum (Discourse), similar to how common issues are handled. Participants supported using the forum over creating new Matrix rooms per incident. Kamil suggested using a special tag in the Discussion forum’s Ask Fedora category for reporting incidents, which could be later converted to a Common Issue if long-lived. It was noted that a clear definition of what constitutes an “incident” would be necessary to avoid tag misuse.
Next Steps: The team focused on the “incident management” part of the proposal. Adam will file a ticket to define a light initial process for incident management. The “production stability/prevention” aspect will be considered in later discussions.
Forgejo Migration Status
The migration to Forgejo is currently paused due to an issue with attachment migration, where all migrated attachments are currently resulting in a 404 error. The team is waiting for a resolution to issue #321 on the Forge project before continuing.
For the time being, users should report / send PRs to the new Forgejo instance (for fedora-easy-karma and issuebot which are migrated) if they find links pointing to Pagure, but should continue using Pagure for anything else until those repositories are migrated.
Test Day / Community Event Status
Kernel 6.18 Test Week: Coming up from 2025-12-14 to 2025-12-20.
FreeIPA Modern WebUI Test Days: Went well last week, with Petr Sklenar organizing. The event was a success, leading to about 80 upstream issues reported in the FreeIPA project, though not all were reflected in the downstream result tracker.
Grub Test Day: May be in the works, related to a specific bugzilla issue.
Open Floor
The next meeting date was tentatively planned for January 5th, as several participants will be on PTO starting December 22nd.