Development/SteeringCommittee/NominationsJune2011

In the May 2011 election, there are 5 seats open. Seats are currently held by: Kevin Fenzi (nirik) (Chair), Bill Nottingham (notting), Kyle McMartin (kyle), Steven M. Parrish (tuxbrewr) and Matthias Clasen (mclasen).

Person Name (IRC nickname)

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

Justin M. Forbes (jforbes)

• Mission Statement: Work to make Fedora a distribution the community can be proud of, with focus on both features and stability. Stressing the balance of new features with QA and release engineering to make Fedora releases both innovative and high quality.
• Past work summary: Original involvement in the Fedora project was working on the port to x86_64. More recently I have been focused on virtualization within Fedora and the Cloud SIG.
• Future plans: Strive to make Fedora the best freely available distribution. Focus on improving improving the developer/tester interaction, the feature process, and general communication with the community.

Peter Jones (pjones)

• Mission Statement: To help make Fedora the best Linux distribution for developers and users.
• Past work summary: I've worked on Linux for Red Hat for more than a decade 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 Fedora's packages for booty, cdparanoia, dumpet, gnu-efi, grub, 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, as well as the upstream maintainer of kernel drivers for iSCSI booting and the UEFI framebuffer. I've served on FESCo in the past, have helped define and refine our policies since before that, and continue to do so.
• Future plans: Continue to help with improvement of our processes, policies, and tools, in order to facilitate building the best OS possible. One important facet of that will be to continue refining the systems and processes for our updates, including improving testing procedures, and making these procedures work better for developers.

Kyle McMartin (kylem)

• Mission Statement: Making Fedora the most cutting edge open source operating system available.
• Past work summary: Kernel in {Fedora, upstream}, Ubuntu, Debian. Loads of parachuted fixes into upstream projects.
• Future plans: Continue to push for better integration of components in Fedora, respect that Fedora is more than the sum of its parts. Push for more active community contribution from upstream communities. Improve polish to compete on the desktop with Ubuntu.

Tomáš Mráz (t8m)

• Mission Statement: To give Fedora back to the hands of the contributors by minimizing bureaucratic and other non-substantial policy restrictions.
• Past work summary: I've been Red Hat employee for more than five years working on packages related to security (PAM, OpenSSL, libgcrypt, GNUTLS, ...) in both Fedora and Red Hat Enterprise Linux. I am one of the upstream maintainers of PAM.
• Future plans: Fedora become too much driven by needs of only a few possible use-cases of modern Linux distribution. In addition to that too many policies in packaging requirements and package update process became "a law" that cannot be broken without approval of FESCo. In some people eyes it makes Fedora a playground for wild changes in some parts of the distribution and impenetrable concrete block in other parts. I do not share this view completely but I can understand why some people have it. My goal is to push for amending the rules to make them more guidance-like than hard laws and at the same time make the maintainers more responsible for their actions if their breaking of the guidances breaks the distribution.

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.

Stephen Gallagher (sgallagh)

• Mission Statement: Make Fedora THE platform for rapidly developing the next generation of free, open-source software.

• Past work summary: Red Hat employee since 2008, Lead developer of the System Security Services Daemon, participant in the FreeIPA project. Fedora Hosted admin deploying ReviewBoard.
• Future plans: Fedora has spent the last couple years veering sharply into the realm of single-user operating system. I think we need to start directing the project back to meeting the needs of small businesses, especially software engineering firms. This means looking into ways to make central management and access control a higher priority for the desktop.

Kevin Fenzi (nirik)

• Mission Statement: To help improve and guide Fedora in continuing to be the best Linux Distro out there.

• Past work summary: Xfce (co)Maintainer for fedora along with many other packages. I have been on FESCo since it was established. Very active on irc trying to improve support in places like #fedora. Fedora Infrastructure Lead as well as somewhat active in rel-eng and many other places in Fedora.

• Future Plans: Try and find ways to ramp up more people to supporting things like engineering-services or doing work that FESCo would like done. Help keep FESCo on track and organized and open.

Iain Arnell (iarnell)

• Mission Statement: Improve the quality of the distribution by promoting more collective responsibility for under-maintained packages.
• Past work summary: Not a Red Hat employee! One of the leading contributors/maintainers of Perl packages within Fedora.
• Future plans: To support the autoqa process, and to ensure the continuation of FTBFS reports.

History

Watch nominations for older elections:

• Winter 2010
• Summer 2010
• Winter 2009
• Summer 2009
• Winter 2008
• Summer 2008
• Summer 2007
• Summer 2006