Hey everyone. As some of you may know we are working on using a agile / sprint type workflow these days. As part of that we have had retrospective/planning meetings just in a video call, but we do all our work in and with the community, so I thought it would make sense to just do this in a matrix meeting and include any community folks who would like to provide input.
We had also decided to combine the release engineering team and infrastructure teams into one meeting, since there's a lot of overlap. So, we are planning the first of these for: 2026-01-26 at 15:00 UTC in #meeting-3:fedoraproject.org General plan for infra: * Look at the current sprint (the one thats ending): https://forge.fedoraproject.org/infra/tickets/projects/325 discuss any retro type things or items that need to continue in the next sprint * Populate the next sprint (next two weeks) some more: https://forge.fedoraproject.org/infra/tickets/projects/326 * close the current sprint * rename the next sprint to current * create a new blank next sprint Then do something similar for release engineering. If we have time we might also see if there's any workflow improvements we can make in this process. kevin -- _______________________________________________ infrastructure mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
