This is a part of the Fedora Linux 43 FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts today, Wednesday 17th December and closes promptly at 23:59:59 UTC on Wednesday, 7th January 2026.
Interview with Fabio Alessandro Locati
FAS ID: fale
Matrix Rooms: I can be easily found in #atomic-desktops:fedoraproject.org, #bootc:fedoraproject.org, #coreos:fedoraproject.org, #devel:fedoraproject.org, #epel:fedoraproject.org, #event-devconf-cz:fedoraproject.org, #fedora:fedoraproject.org, #fedora-arm:matrix.org, #fedora-forgejo:fedoraproject.org, #fosdem:fedoraproject.org, #flock:fedoraproject.org, #golang:fedoraproject.org, #iot:fedoraproject.org, #meeting:fedoraproject.org, #meeting-1:fedoraproject.org, #mobility:fedoraproject.org, #python:fedoraproject.org, #rust:fedoraproject.org, #silverblue:fedoraproject.org, #sway:fedoraproject.org, #websites:fedoraproject.org
This is a part of the Fedora Linux 43 FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts today, Wednesday 17th December and closes promptly at 23:59:59 UTC on Wednesday, 7th January 2026.
Interview with Dave Cantrell
FAS ID: dcantrell
Matrix Rooms: Looking right now it appears Fedora Council, FRCL, Introductions, Announcements, Fedora Meeting, and Fedora Meeting 1. I tend to go to rooms that people ask me to join. I also use it a lot for DMs and people find me that way. For me primarily I rely on Matrix for our online meetings and DMs with people. Email continues to be the most reliable way to reach me and have a conversation.
December 17, 2025 / Justin Wheeler / Comments Off on F43 FESCo Elections: Interview with Zbigniew Jędrzejewski-Szmek (zbyszek)
This is a part of the Fedora Linux 43 FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts today, Wednesday 17th December and closes promptly at 23:59:59 UTC on Wednesday, 7th January 2026.
TL;DNR: The Fedora Linux 43 Election schedule has been extended. Voting will now take place from 15 December 2025 through 7 January 2026.
Due to unforeseen delays in the interview coordination process, we are adjusting the election timeline. To ensure all candidates have ample opportunity to present their platforms and the community has sufficient time to vote, the election period will now extend through the year-end holidays.
Please mark your calendars with the following new critical dates:
📅 New Election Schedule
Interview Submission Deadline (Extended): Now through Friday, 12 December 2025 at 23:59 UTC(Candidates: Please ensure your responses are submitted by this time.)
Voting Setup & Interview Publishing:Monday, 15 December 2025(Voter guides and interviews will be published to the community on this date.)
Voting Period Opens:Monday, 15 December 2025
Voting Period Closes:Wednesday, 7 January 2026 at 23:59 UTC
This is a summary of the work done by Fedora Infrastructure & Release Engineering teams as of Q3 2024. As these teams are working closely together, we will summarize the work done in one blog post by both teams.
This update is made from infographics and detailed updates. If you want to just see what’s new, check the infographics. If you want more details, continue reading.
This is a summary of the work done on initiatives by the CPE Team. Every quarter, the CPE team works together with CentOS Project and Fedora Project community leaders and representatives to choose projects that will be being worked upon in that quarter. The CPE team is then split into multiple smaller sub-teams that will work on the chosen initiatives + day-to-day work that needs to be done. Some of the sub-teams are dedicated to the continuous efforts in the team whilst some are created only for the initiative purposes.
This update is made from infographics and detailed updates. If you want to just see what’s new, check the infographics. If you want more details, continue reading.
Flock to Fedora 2024, held in Rochester, New York from August 7th to 10th, soared to new heights, bringing together Fedora contributors and enthusiasts for four days of immersive learning, dynamic collaboration, and vibrant community building. The event seamlessly blended in-person interactions with live stream and recorded sessions via YouTube for the first two days, ensuring accessibility for a wider audience. Using Matrix Chat for seamless communication and a well-structured online schedule, Flock 2024 successfully fulfilled its mission of uniting the Fedora community, fostering connections, and sparking a wave of innovation.
Target Audience
The primary target audience was Fedora contributors, encompassing developers, packagers, designers, documentation writers, and anyone actively involved in the Fedora Project. The event also welcomed newcomers and those curious about Fedora and open source.
Attendees
Rochester welcomed a diverse and passionate group of attendees, including, but not limited to:
The majority of the Fedora Council, FESCo, and Mindshare Committee members.
Fedora Project Leader Matthew Miller, Fedora Operations Architect Aoife Moloney, Fedora Community Architect Justin W. Flory
Representatives from sponsor communities, like Rocky Linux, Lenovo, Microsoft Azure, AlmaLinux, CentOS, openSUSE, ARM, Meta, and SureStep.
Numerous passionate Fedora community members. See badge scans for a full list.
Key Highlights From The Event
Engaging Keynotes: Matthew Miller’s “State of Fedora” keynote provided valuable insights into the project’s trajectory. Other impactful keynotes included Pat Riehecky’s “It is OK not to know things” and Anita Zhang’s “How (Not) To Get Into Tech,” offering diverse perspectives on the open source journey.
Dynamic Sessions and Workshops: The event featured many sessions catering to diverse interests, with popular choices including panel discussions from the Fedora Council and FESCo, “What does Red Hat want?”, and numerous talks on Bootc.
Diverse Tracks: Attendees explored three tracks, including the Flock general track, the CentOS track, and the Mentor Summit track. These tracks tool place across several rooms, like the Red Hat main stage, and the breakout rooms sponsored by Lenovo, Rocky Linux, and Microsoft Azure. Topics ranged from technical deep dives (OpenQA, Konflux, eBPF, AI/ML, RISC-V) to community-building initiatives and DEI efforts.
International Candy Swap: This unique tradition fostered cross-cultural connections as attendees shared sweets and stories from their home countries.
Fedora Community Engagement
The Fedora community was actively involved throughout the event.
Community members contributed as speakers, workshop leaders, and attendees, driving discussions and knowledge sharing.
Topics like Bootc and the future of Fedora sparked lively conversations and collaboration.
Community Participation and Recognition
Booth Staff/Volunteers: The dedicated volunteer team, including those listed on the Flock 2024 – Volunteers sign-up sheet, ensured a smooth and welcoming experience for all attendees. Their tireless efforts were critical to the event’s success.
Speakers: A diverse group of speakers shared their expertise and insights, fostering learning and inspiring attendees. Myself and two of my fellow interns, Adrian Edwards and Roseline Bassey, presented a hybrid presentation of pre-recorded and live sessions as part of the Mentored Projects Showcase. You can see the full speaker list on the conference schedule.
Virtual Events
Livestream & Recordings: The event’s first two days were live-streamed and recorded, allowing virtual participants to engage with the content.
Viewership Data:
Day 1:
Red Hat Room: Over 1,000 views
Lenovo Room: 888 views
Rocky Linux Room: 427 views
Microsoft Azure Room: 324 views
Day 2:
Red Hat Room: 674 views
Lenovo Room: 288 views
Rocky Linux Room: 286 views
Azure Room: 213 views
Online Engagement: Social media platforms buzzed with activity, with attendees and virtual participants sharing their experiences and insights using the official hashtags #FlockToFedora, and #FlockRochester.
Challenges, Lessons Learned, and Recommendations
Streaming Capabilities: Available resources constrained our ability to live stream the entire event, while the impact of this for virtual attendees was minimized with creative scheduling, the hope is to explore improvements to the event streaming setup in the future.
Weather Disruption: The scavenger hunt was unfortunately affected by a storm, highlighting the importance of contingency plans for outdoor or weather-dependent activities.
Survey Feedback: We conducted a post-event attendee survey to collect feedback from attendees and speakers. This valuable input has guided us and will continue to guide us in implementing improvements and addressing areas of concern for future Flock events.
Conclusion
Flock to Fedora 2024 was a success, showcasing the strength and vibrancy of the Fedora community. We are already looking forward to Flock to Fedora 2025! To stay informed about future events and opportunities to get involved, visit the Fedora Project website, join the Fedora Matrix room, and follow us on social media!
Special Thanks to Our Sponsors
We extend our deepest gratitude to all our sponsors, whose generous support made Flock to Fedora 2024 possible. Your commitment to open source and the Fedora community is invaluable.
This change is being made to reflect actual practice. For example, there is clear overlap between the use-cases and potential user-bases for the current Server, Cloud, and CoreOS Editions, but each takes a different approach. We are currently considering adding an exception for a KDE Desktop Edition, which would overlap with Fedora Workstation.
Currently part of the policy currently reads in a way that prevents this exception from being possible:
A Fedora Edition:
addresses a distinct, relevant, and broad use-case or user-base that a Fedora Edition is not currently serving;
is a long term investment for the Fedora Project; and
is consistent with all of Fedora’s Four Foundations.
We propose an additional line:
The Council may make exceptions to the “distinct” rule when we determine that doing so best fits the Project’s Mission and Vision.
This topic is open for community discussion, following our Policy Change Policy. After two weeks, the Council will vote in a new ticket, and if approved, the policy will be updated.
Approval of this change would not automatically mean the approval of a KDE Desktop Edition, but would allow that possibility.
Recent Comments