This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Thursday, 21 November and closes promptly at 23:59:59 UTC on Thursday, 5 December 2019.

Interview with Kevin Fenzi

  • Fedora account: kevin
  • IRC nick: nirik (found in #fedora-noc, #fedora-apps, #fedora-admin, #fedora-devel, #fedora, many more…)
  • Fedora user wiki page


Describe some of the important technical issues you foresee affecting the Fedora community. What insight do you bring to these issues?

I think that modularity and the issues around it are going to continue for a while. I hope I can provide some help in bringing the ‘lets drop modularity and forget it happened’ and the ‘lets modularize everything’ camps together on some solution that works not only for Fedora, but our downstream distros too.

What objectives or goals should FESCo focus on to help keep Fedora on the cutting edge of open source development?

I think we really should look at a rework of our packaging workflow. Many of the things we setup in the past don’t make as much sense as they did then. Something like using signed tags to let the automation know what you want (build for X Y Z, or please run the CI on a build of this, or whatever). It’s not going to be easy, but I think if we design things right it will be a lot less work on our packagers.

What are the areas of the distribution and our processes that, in your opinion, need improvement the most? Do you have any ideas how FESCo would be able to help in those “trouble spots”?

Well, the workflow as noted. I think we just need to come up with a good framework and let the community help fill in the blanks. We did gather some good info on the devel list recently.