Fedora Community Blog

Page 6 of 184

Throwing Random Arguments at System Binaries: Real Segfaults vs. Ticket Noise

April 28, 2026 / Petr Sklenar / 2 Comments

Why Would Anyone Do This?

Two and half reasons:

Smoke testing – You want to know if your system commands actually work, not just when you run them the way the docs say, but when users (or their scripts) feed them garbage.
AI is excellent at generating potential edge cases, and tracking systems are already all too eager to collect new tickets. I’m being careful not to dump every AI finding into Bugzilla; I don’t want to clutter the backlog and mainly waste developer time on theoretical bugs. Or Should I?

Plus, segfaults don’t lie – either the system crashed or it didn’t, and those are the issues that actually deserve the ticket.

Community Update – Week 17 2026

April 24, 2026 / zlopez / Comments Off

This is a report created by CLE Team, which is a team containing community members working in various Fedora groups for example Infrastructure, Release Engineering, Quality etc. This team is also moving forward some initiatives inside Fedora project.

Week: 20 – 24 April 2026

Fedora Verified: Help Shape a New Way to Recognize Fedora Contributors

April 21, 2026 / Ananya Nalavathu / 16 Comments

The Fedora Project is proposing a new contributor status called “Fedora Verified” to better recognize all forms of community contribution, and we need your feedback. Following the Fedora Council 2026 Strategy Summit, Fedora leadership is reflecting on how we recognize, support, and empower the people who make Fedora possible. Please read through our proposal below and share your thoughts in the Fedora Verified community survey.

Community Update – Week 16

April 17, 2026 / lenkaseg / Comments Off

Week: 13 – 17 Apr 2026

Community Update – Week 15 2026

April 10, 2026 / lenkaseg / Comments Off

Week: 06 – 10 Apr 2026

Marie Nordin © CC BY-SA 4.0

Fedora Code of Conduct Report 2025

April 7, 2026 / Chris Idoko / Comments Off

The Fedora Project’s Code of Conduct and its reports are managed by the Fedora Code of Conduct Committee, the Fedora Community Architect, and the Fedora Project Leader. We publish this summary to demonstrate our commitment to community safety and our project’s social fabric.

This post covers the year of reports received in the 2025 calendar year. The purpose of publishing the annual Code of Conduct Report is to provide transparency, insight, and awareness into the health signs of the community.

Community Update – Week 14 2026

April 3, 2026 / zlopez / Comments Off

Week: 31 Mar – 03 Apr 2026

Fedora Code of Conduct Report 2024

April 2, 2026 / Chris Idoko / 3 Comments

This post covers the year of reports received in the 2024 calendar year. The 2023 and 2024 annual report posts are published with delays due to changes in membership in the Code of Conduct Committee and rebalancing existing work. The purpose of publishing the reports now is to provide transparency, insight, and awareness into the health signs of the community.

Fedora Code of Conduct Report 2023

March 31, 2026 / Chris Idoko / 3 Comments

This post covers the year of reports received in the 2023 calendar year. The 2023 and 2024 annual report posts are published with delays due to changes in membership in the Code of Conduct Committee and rebalancing existing work. The purpose of publishing the reports now is to provide transparency, insight, and awareness into the health signs of the community.

The forge is our new home.

March 24, 2026 / Tomáš Hrčka / 20 Comments

After a full year of preparation, the Community Linux Engineering (CLE) team is excited to announce that Fedora Forge, powered by Forgejo, is ready for use! We are proud of this modern Open Source platform and what it means for the future of Fedora Infrastructure. While pagure.io has been a vital part of our community for many years, the time has come to retire our homegrown forge and transition to this powerful new tool.