From Fedora Project Wiki
The nomination period is CLOSED
The nomination period ended at 23:59:59 UTC on May 25, 2013.

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

Introductions

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


Questionnaire

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

Candidates

User1 (user_1)

Introduction

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

Questionnaire

  • Question1?
    • Answer1

Kevin Fenzi (kevin)

Introduction

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: https://admin.fedoraproject.org/pkgdb/users/packages/kevin

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)

Introduction

  • 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)

Introduction

  • 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 ensure that our processes for developers are as simple as possible, and to avoid processes that result in unnecessary work, or in duplication of effort, as we form new rules for change management in Fedora. 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.

Tomáš Mráz (t8m)

Introduction

  • Mission Statement:

Keeping Fedora as an usable and good quality operating system for running server and desktop applications.

  • Past work summary:

I've been Red Hat employee and Fedora contributor for more than eight 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. I was FESCo member for the past two years.

  • Future plans:

Apart from trying to adhere in my FESCo work to the mission statement above I'd like to help with implementation of the new change process and the Fedora revamp proposal. I'd also like to bring at least slightly more democracy into the FPC membership process.

Matthew Miller (mattdm)

Introduction

  • Mission Statement:
    • To see the Fedora distribution become more widely used as a platform, with modular layers of enabling technology all within the wider circle of the Fedora community.
  • Past work summary:
    • I've worked with Fedora since the beginning, as a community member and in my various roles as sysadmin and systems architect at Boston University and Harvard. (At BU, I helped host the very first FUDCons.) I've maintained a number of small packages for a long time. I was hired by Red Hat last year to work on Fedora Cloud, and have been working with others in the Cloud SIG to add polish to our Cloud images. I'm also on the Minimal Core SIG, which I care about both for the cloud images and because changes there ripple out and affect everyone. I'm often active on the mailing lists, and while I sometimes have strong opinions, I know I'm not always right and therefore try very hard to listen to all the different viewpoints.
  • Future plans:
    • I have a somewhat active vision for a Fedora project, centered around a base platform and with greater latitude for SIGs to solve problems within their areas. I'd like to see a more carefully managed (but not stagnant!) core OS, while allowing other layers to be less perfect when perfection is getting in their way — yet still hold those layers to standards agreed on by the Fedora community. Without both of these things, we risk becoming irrelevant: either beautiful but rarely used, or completely marginalized as we're passed by. Fedora is the best enthusiast distribution, and it can also be the best platform for development, the best cloud environment, and the base for a polished end-user experience.

Josh Boyer (jwb)

Introduction

  • Mission Statement:
    • To ensure Fedora remains a high quality, leading edge distribution with a variety of uses.
  • Past work summary:
    • I have been a Fedora user since its inception, and a Fedora contributor since around Fedora Core 4. In the past I've held positions on the Fedora Board and Fedora rel-eng teams. I was also part of the PowerPC secondary architecture effort. I've been on FESCo off and on since 2006. I am currently one of the three Fedora kernel maintainers, and I am a FESCo member running for re-election.
  • Future plans:
    • Continue to let developers and contributors accomplish what they need with a minimum amount of process and overhead. Help with the new change process as it evolves. Continue to look at the distro as a whole with an eye on improving the usability and function for a variety of targets.

Kalev Lember (kalev)

Introduction

  • Mission Statement:
    • Make sure Fedora stays relevant for both end users and developers.
  • Past work summary:
    • Fedora contributor for over 4 years, provenpackager and packager sponsor.
    • Co-handling the GNOME mass builds in Fedora.
    • Contributor to upstream GNOME.
    • Involved with the Fedora MinGW SIG since its beginning.
  • Future plans:
    • Try to make Rawhide a more usable platform for day-to-day use.
    • Fine tune the Branched release schedule and release engineering workflow to minimize rawhide bitrot. Right now Branched gets a lot of undivided attention for nearly 4 months before the release, and developers are off rawhide during that time.
    • Get Fedora back on track with its 6-month schedule, synced with upstreams that release every 6 months.
Retrieved from "https://fedoraproject.org/w/index.php?title=Development/SteeringCommittee/Nominations&oldid=339247"