Across the Fedora Project, multiple groups are heavily focused on preparing for the upcoming Fedora 44 (F44) release. A significant amount of work is dedicated to the mass branching event, with teams like Releng, Infrastructure, and Quality coordinating efforts, testing changes, and fixing build failures that have been exposed by mass rebuilds. Another major cross-team effort is the migration from Pagure to the new Forgejo platform (Forge). The Docs, Quality, and Infrastructure teams are all actively moving repositories, tickets, and documentation, as well as adapting their workflows and tooling to the new system. Finally, with the Flock conference's Call for Proposals deadline approaching, several groups, including CoreOS, Server, and the Atomic Initiative, are planning and discussing potential talks and Birds of a Feather (BoF) sessions to submit.

AI & ML SIG

The group's main focus was on preparing for the F44 release, as the mass rebuild has highlighted several broken Python packages. A significant issue with PyTorch causing segfaults on aarch64 is being tracked. Fixes are in progress for ROCm packages to reduce build times, but updates to other packages like ollama are paused until the branching issues are resolved. The SIG is also actively seeking more contributors for packaging tasks. A discussion on a new package review for ggml was postponed, with concerns raised about its fast-moving nature making it difficult to maintain.

• Decisions:
  • Work on ollama and other package updates is paused until F44 branching issues are stable.
  • The ggml package review was postponed to the next meeting.
• Important Subjects:
  • F44 branch readiness and fixing broken Python packages.
  • Recruiting new contributors to the AI Packagers SIG.
  • Maintenance concerns for fast-developing packages like ggml.

CoreOS

The team worked on resolving build failures for FCOS rawhide caused by systemd-pam being dropped from systemd dependencies. A temporary workaround was decided upon to unblock builds. They also reviewed several F44 changes, noting that the Podman 6 update may not land in F44 and that the signature checking change has been deferred to F45. The group's proposal to build on Konflux is currently blocked by an artifact signing issue. Planning for the Flock conference is underway, with a lab on k3s and a general "image mode" BOF being considered.

• Decisions:
  • A temporary workaround will be implemented to add systemd-pam directly to the FCOS package list to fix rawhide builds.
  • The tracker issue for the signature checking change will be updated to target Fedora 45.
• Important Subjects:
  • Fixing FCOS rawhide build failures.
  • The Konflux build signing workflow issue, which is blocking their F44 change proposal.
  • Planning for submissions to the Flock conference CFP.

Docs SIG

The team reviewed and approved a three-phase plan to modernize the Fedora Docs homepage, which involves migrating the repository to Forgejo, reviewing content, and implementing the new design. All action items from the previous meeting were completed. They also noted the upcoming CFP deadline for the Flock conference and planned their presence at FOSDEM and CentOS Connect. A discussion on a recent analysis of Quick Docs content was started, with the goal of using it to create "good first issues" for new contributors.

• Decisions:
  • Adopted a three-phase plan for the Docs homepage modernization.
  • The homepage repository will be migrated from GitLab to Forgejo.
• Important Subjects:
  • Redesigning the Fedora Docs homepage.
  • Migration of team documentation and repositories to Forgejo.
  • Analyzing Quick Docs content to improve contribution pathways.

FESCO

The meeting was canceled because there were not enough members present to form a quorum.

• Decisions:
  • None.
• Important Subjects:
  • None.

Fedora Atomic Initiative

The group discussed a proposal for a "Birds of a Feather" (BoF) session at the upcoming Flock conference to promote the Atomic initiative and bootc. A significant technical roadblock was identified concerning the F44 change proposal to use Konflux for builds: artifacts built this way are not signed by an official Fedora key. Two potential solutions were discussed, either distributing the Konflux key via Fedora Security or creating a new Tekton task for signing container images.

• Decisions:
  • The Konflux artifact signing issue will be brought to the Konflux steering group for next steps.
• Important Subjects:
  • Planning a BoF session for the Flock conference.
  • The critical issue of unsigned artifacts being produced by Konflux builds.

Go SIG

The team is actively preparing for the upcoming Go 1.26 release. A mass rebuild is underway in COPR to test Go 1.26rc2 against Fedora packages. In preparation for new compiler rules, upstream fixes were submitted for the gh and rclone packages to ensure they remain compatible. Team members are also reviewing their own packages for any issues related to the new vet rules.

• Decisions:
  • None explicitly stated, but actions imply a decision to proactively test and fix packages for Go 1.26 compatibility.
• Important Subjects:
  • Testing Go 1.26rc2 with a mass rebuild.
  • Ensuring Fedora packages are compatible with new vet rules in Go 1.26.

Infra & Releng

This joint meeting was dedicated to sprint planning using the new Forge platform. The teams agreed that project boards should be created at the organization level to allow tickets from multiple repositories to be included in a sprint. The Infra team's upcoming sprint will have lower capacity due to team members attending FOSDEM, with a focus on Forge migration and day-to-day tasks. The Releng team's primary goal for their sprint is the complex mass branching for the next Fedora release, scheduled for February 3rd.

• Decisions:
  • Project boards for both Infra and Releng will be created at the organization level on Forge.
  • Unplanned work will be tagged with a day-to-day label for better tracking.
• Important Subjects:
  • Adopting the Forge platform for Agile sprint planning.
  • Preparing for the F44 mass branching event.
  • Managing team capacity during FOSDEM.

Infrastructure

Across several meetings, the team focused on daily operations, ticket triage, and the ongoing migration to the new Forge platform. This migration work includes moving repositories, updating meeting bots to use new URLs, and getting fedora-messaging working on Forge. They managed several hardware and service issues, including network card problems, a failed disk, and rebooting OpenShift workers and Koji hubs. The team is also involved in preparing for the upcoming mass branching event.

• Decisions:
  • Triaged multiple new tickets, assigning priority and points.
  • The infrastructure project board was moved to a new organization-level URL on Forge.
• Important Subjects:
  • Migrating infrastructure, repositories, and tooling to the new Forge platform.
  • Managing hardware issues and planned maintenance (mass reboots).
  • Supporting the upcoming F44 mass branching.

Internationalization

The team is preparing for the Fedora 44 cycle. Their F44 Change proposals are awaiting FESCo approval. A key decision was made to move the F44 i18n test week from its initial date to March 9th to better align with the GNOME 50 release candidate schedule. This alignment will become part of the team's criteria for scheduling future test weeks. A significant backlog of 48 bugs for Fedora 42 still needs to be triaged.

• Decisions:
  • The Fedora 44 i18n test week was rescheduled to start on March 9th.
• Important Subjects:
  • Getting F44 Changes approved by FESCo.
  • Triaging the bug backlog for Fedora 42.
  • Coordinating test week schedules with upstream releases like GNOME.

Quality

The group is focused on the F44 release, which is scheduled to branch on February 3rd. They are investigating multiple failures in openQA compose tests and noted that many recently approved F44 Changes are missing their tracking bugs. The migration of QA repositories from Pagure to Forgejo is nearly complete, and the team is now using Forgejo Projects for sprint planning. A follow-up task is to standardize labels across the newly migrated repositories. Planning for future Test Days is also underway.

• Decisions:
  • The Red Hat QA team will now use Forgejo Projects for public sprint planning.
• Important Subjects:
  • Investigating and resolving openQA test failures for F44.
  • Completing the migration of QA repositories to Forgejo.
  • Ensuring F44 Changes have proper tracking bugs for testing.

Releng

The team's primary focus across two meetings was the upcoming F44 mass branching scheduled for February 3rd. They discussed and clarified several points of confusion in the Standard Operating Procedure (SOP) and will use a new Ansible playbook to automate part of the process. Due to a key member's unavailability, patrikp will lead the effort with support from nirik. The team also discussed breaking the large mass branching task into smaller, dependent tickets on Forge for better tracking. The long-term task of migrating fedpkg to use the new Forge platform was also discussed, acknowledging its complexity.

• Decisions:
  • patrikp will lead the F44 mass branching process.
  • The large mass branching task will be broken down into smaller sub-tasks on Forge.
  • status.fedoraproject.org will be used to communicate the status of the branching to the community.
• Important Subjects:
  • Detailed planning and clarification of the F44 mass branching procedure.
  • Adopting new automation and ticketing practices for mass branching.
  • The technical challenges of migrating core tooling like fedpkg to Forge.

Server SIG

The group discussed submitting a proposal for the Flock conference, likely a Birds of a Feather (BoF) session. Progress on creating their working plan has been slow. The most urgent topic was the need for testing the next release (Fedora 44), as the branch date is imminent. They identified that the KVM and aarch64 Server images are flawed and require immediate testing.

• Decisions:
  • The meeting for February 4th was canceled to allow members time for preparatory work on testing and Flock submissions.
• Important Subjects:
  • Urgent testing required for flawed F44 KVM and aarch64 server images.
  • Submitting a proposal for the Flock conference.
  • Slow progress on the group's working plan.

This summary has been AI-generated. If you see errors, please email aurelien@bompard.org or reach out to @abompard:fedora.im on Matrix, and they will be corrected.