From Fedora Project Wiki
We're OPEN!
The nomination period is in progress!

The following elections will take place in May/June 2013:

All dates and times noted are UTC time.

FESCo Elections May/June 2013

These members were elected in the last elections:

As per the FESCo election policy, the following finish their terms, and the seats are up for re-election:

More information at the FESCo wiki page.

For the last election, see NominationsMayJune2012

Eligible Voters
Voting eligibility is determined by a community member's Fedora Account System (FAS) memberships.

To vote for FESCo you must have cla_done + one other "non-cla" group in FAS.

Candidate template


  • Mission Statement:
  • Past work summary:
  • Future plans:


The questions have not been posted. Please wait for the questionnaire wrangler to contact you!
  • Question 1


User1 (user_1)


  • Mission Statement:
  • Past work summary:
  • Future plans:


  • Question1?
    • Answer1

kevin (Kevin Fenzi)


I have long been a Fedora contibutor and I'd like to continue to help guide Fedora's Technical decisions.

  • Mission Statement:

To continue to guide techincal decisions in Fedora and help others get done the things that help our community.

  • Past work summary:

Package maintainer since the extras days:

I co-maintain the Xfce desktop packages.

Work with release engineering

I have served on FESCo for a long time.

Employed as Fedora Infrastructure lead to keep all our various infrastructure going.

Lots of other things...

  • Future plans:

Finish process changes to get Features moved to Changes and help streamline tracking.

Clean up and modernize some of our policies, especially non responsive maintainers policy.

Bill Nottingham (notting)


  • Mission Statement:
    • I plan to represent the Fedora community in FESCo with an eye towards maintaining the quality and standards of the Fedora distribution, including features, testing, stability, release engineering, and so on.
  • Past work summary:
    • Red Hat employee since 1998, developer on Red Hat Linux since 5.1, Fedora contributor since its inception, FESCo member, Fedora board member, Release engineering team member, and assorted other roles.
  • Future plans:
    • Continue to make Fedora the best freely available distribution anywhere. Work with those that show up to make changes, as, realistically, FESCo does not have a significant amount of resources to direct.

Peter Jones (pjones)


  • Mission Statement:
    • I'll continue to work to maintain a high level of technical feasibility and avoid micromanagement in decisions made by FESCo. I'll try to streamline our processes for developers, and to avoid processes that result in unnecessary work, or in duplication of effort. As I've shown in the past, I'll continue to try to guide our policy decisions to put the power and responsibility in developers hands rather than requiring FESCo's or other committee's intervention and participation at every level.
  • Past Work Summary:
    • I've worked on Linux for Red Hat since 1998 in various roles including technical support and engineering. I'm one of the anaconda maintainers as well as the maintainer of (thankfully now deprecated) mkinitrd, and am or have been maintainer of Fedora's packages for booty, cdparanoia, dumpet, gnu-efi, grub, grub2, grubby, python-pyblock, syslinux, and others. I've worked on many levels of our software stack, including implementing installation and boot support for iSCSI, UEFI, dmraid, from the kernel all the way up through userspace. I also represent Red Hat and Fedora on the UEFI Specification Working Group. I'm currently a member of FESCo seeking re-election, and have been serving in this capacity since the winter election of 2009.
  • Future Plans:
    • I'm currently focused on implementing and impoving UEFI support throughout Fedora. As a FESCo member I'll continue to help ensure that developers have what they need to implement their features and bug fixes with as little hindrance as possible, and at the same time avoid unnecessary and wasted effort, especially as we revamp the Feature process.