This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Wednesday, January 17th and closes promptly at 23:59:59 UTC on Wednesday, January 24th, 2018.
Interview with Kevin Fenzi (kevin)
- Fedora Account: kevin
- IRC: nirik (found in most #fedora* channels)
- 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 the coming year will continue to see technical issues around how we make Fedora. There is going to be lots more modularity work that should make it much easier to maintain packages, along with continuing container and other ways to consume Fedora. I think I bring a great deal of history to this discussion so I can make sure we learn from our mistakes.
What objectives or goals should FESCo focus on to help keep Fedora on the cutting edge of open source development?
Modules and Automation. We should free our maintainers to do the hard interaction work (fixing bugs, helping users communicate with upstream, making things better) instead of grunt work. More automated testing and module building should help this a great deal.
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”?
We have a number of areas for improvement, but I think FESCo’s job is to coordinate and help people doing work on this spots so they can make things better.