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 Kevin Fenzi

  • FAS ID: kevin
  • Matrix Rooms: I’m probibly most active in the following rooms. I’m available and answer notifications and watch many other channels as well, but those 3 are the most active for me:
    • noc -> day to day infra stuff, handling alerts, talking with other infra folks
    • admin -> answering questions, helping fix issues, some team discussions
    • releng -> release engineering team discussions, answering questions, handling issues, etc.

Questions

Why do you want to be a member of FESCo and how do you expect to help steer the direction of Fedora?

I think I still provide useful historical information as well as being able to pull on that long history to know when things are good/bad/have been tried before and have lessons to teach us.

Based on the proposals we approve or reject we can steer things from FESCo. I do think we should be deliberate, try and reach consensus and accept any input we can get to try to come to good decisions. Sometimes things won’t work out that way, but it should really be the exception instead of the rule.

How do you currently contribute to Fedora? How does that contribution benefit the community?

I’m lucky to be paid by Red Hat to work on infrastucture, I like to hope it’s useful to the community
In my spare time I work on packages, answering questions where I can, unblocking people, release engineering work, matrix and lists moderation.

I really hope my contributions contribute to a happier and more productive community.

How do you handle disagreements when working as part of a team?

I try and reach consensus where possible. Sometimes that means taking more time or involving more people, but If it can be reached I think it’s really the best way to go.

Sometimes of course you cannot reach a consensus and someone has to make a call. If thats something I am heavily involved in/in charge of, I do so. I’m happy that we have a council as a override of last resort in case folks want to appeal some particularly acromonious decision. Also, as part of a team you have to sometimes delegate something to someone and trust their judgement in how it’s done.

What else should community members know about you or your positions?

I think there’s been a number of big debates recently and probibly more to come. We need to remember we are all friends and try and see things from other people’s point of view.

My hero these days seems to be treebeard: “Don’t be hasty”

My matrix/email is always open for questions from anyone…