Development/SteeringCommittee/Nominations

We're OPEN!
The nomination period is in progress!

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

• Fedora Project Board (three seats)
• FESCo (Engineering) (four seats)
• FAmSCo (Ambassadors) (three seats)
• Fedora 19 Name (separate schedule from the committee elections)

All dates and times noted are UTC time.

FESCo Elections May/June 2013

These members were elected in the last elections:

• Toshio Kuratomi (abadger1999)
• Miloslav Trmač (mitr)
• Marcela Mašláňová (mmaslano)
• Stephen Gallagher (sgallagh)

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

• Kevin Fenzi (nirik)
• Bill Nottingham (notting)
• Peter Jones (pjones)
• Josh Boyer (jwb)
• Tomáš Mráz (t8m)

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 (Kevin Fenzi)

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.