*Note: This summary is AI-generated but has been validated by at least one of the attendants.*

*   **General**
    *   `nirik` was not present at the meeting.
*   **Ticket Review**
    *   **[#13226](https://forge.fedoraproject.org/infra/tickets/issues/13226):** The group agreed to classify this ticket as low priority, 2 points, and day2day.
    *   **[#13227](https://forge.fedoraproject.org/infra/tickets/issues/13227):** The group agreed to classify this ticket as medium priority, 3 points, and day2day.
        *   **Action:** Someone with hardware service experience needs to be contacted, but it's unclear who that is.
    *   **[#13229](https://forge.fedoraproject.org/infra/tickets/issues/13229):** The ticket is a user-facing issue with `grub2` and secure boot, not an infrastructure problem.
        *   `jcline` noted a recent change in the secure boot signing process (moved to the sigul server) which may be related to the issue reported in the ticket and by others on a Bodhi update.
        *   **Action:** `james` will close the ticket and comment, directing the user to file a bug in Bugzilla against the `grub2` component and explaining the scope of the infrastructure team.
*   **Planning, Upcoming work and Open floor**
    *   `james` completed system updates the previous night and has since fixed some related issues with the `updates+uptimes` code.
    *   One machine failed to come back up after a reboot during the updates.