Development/SteeringCommittee/Nominations

We're OPEN!
The nomination period is in progress! Please add your nomination before 23:59:59 UTC on January 19, 2015!

The following elections will take place in January 2015:

• FESCo (Engineering) (five seats)
• Environment and Stacks Working Group (four seats)

All dates and times noted are UTC time.

FESCo Elections January 2014

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

• Kevin Fenzi (nirik) elected for F20/F21 term
• Tomas Hozza (thozza) elected for F20/F21 term
• Kalev Lember (kalev) elected for F20/F21 term
• Matthew Miller (mattdm) elected for F20/F21 term
• Tomáš Mráz (t8m) elected for F20/F21 term

More information at the FESCo wiki page.

For the last election, see Nominations July 2014

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.

Candidates

User1 (user_1)

Introduction

• Mission Statement:

• Past work summary:

• Future plans:

Kevin Fenzi (nirik)

Introduction

I've been involved with Fedora for almost 10 years now. I would like to continue to help guide technical decisions and make Fedora the best it can be.

• Mission Statement:
  • To provide information and history to keep Fedora on track to being the best.

• Past work summary:
  • (co)Maintainer of Xfce packages
  • Tons of other packages: https://admin.fedoraproject.org/pkgdb/users/packages/kevin
  • Employed by Red Hat to lead Fedora Infrastructure
  • Lots of work with releng tasks helping out where I can.
  • I use both Xfce and Gnome3 these days (switching off)
  • I help out users in #fedora, fedora-users list and (time permitting) fedora-forum.

• Future plans:
  • Keep Fedora 22 on track.
  • Rework the non responsive maintainer process (I know, I know, I have said I would before, but it really needs it).

Parag Nemade (paragan)

Introduction

A core Free and Open Source software engineer. I've been using Fedora since its very first release Fedora Core 1.

• Mission Statement:
  • To make Fedora the _best_ technology platform for users and developers alike.

• Past experience:
  • One of the leading package maintainer & a sponsor for Fedora. (my packages)
  • Active participant in devicing packaging guidelines, doing package reviews, grooming new packagers, fedora-qa, everything related to packages.
  • Employed by Red Hat in i18n group.
  • Love to help fellow Fedora users on lists and IRC.

• Future plans:
  • To sanitise and improve the package base in Fedora.
  • Continue to participate in making Fedora the _best_ technology distribution.

Adam Jackson (ajax)

Introduction

I've deleted things you people wouldn't believe...

• Mission Statement:
  • Fix problems, don't paper over them.

• Past work summary:
  • Fedora and RHEL (co)maintainer for X11 and Mesa for 9+ years
  • Casual maintenance for a bunch of other stuff
  • Driveby contributions, mass rebuilds, and other broken-window work on pretty much the whole OS
  • At least one prior tour of duty on fesco

• Future plans:
  • Reconcile the divergent demands of different product streams to mutual benefit
  • Identify pain points and bottlenecks in Fedora development and consumption processes (and render them unto the past tense)

Debarshi Ray (rishi)

Introduction

I am currently working on Fedora Workstation, and I joined the project in 2007.

• Mission Statement:
  • Make Fedora more usable as an end-user facing (or client-side) operating system.

• Past work summary:
  • Back port and issue fixes for various GNOME components.
  • Employed by Red Hat to work on Workstation, particularly GNOME.

• Future plans:
  • Try to sanitize our updates process.

David King (amigadave)

Introduction

GNOME developer, working on Fedora Workstation.

• Mission Statement:
  • Ensure smooth communication between working groups and FESCo, enabling a successful Fedora 22 and beyond

• Past work summary:
  • GNOME developer for several years, maintaining several modules
  • Red Hat employee for just under 2 years, working on Fedora Workstation
  • I maintain some GNOME and MinGW packages in Fedora, and help out in the gnome-sig group

• Future plans:
  • Support the activities of Working Groups, especially Workstation

Alberto Ruiz (aruiz)

Introduction

GNOME developer, Fedora Workstation contributor and Fleet Commander maintainer.

• Mission Statement:
  • I would like to ensure

• Past work summary:
  • Red Hat employee for about two years as the manager of the desktop apps team, working on Fleet Commander as of now
  • Worked for Canonical for two years in the Unity team
  • GNOME developer since 2005
  • I maintain ino a package for command line Arduino development

• Future plans:
  • I want to make Fedora make the most ofthe new multiple product strategy
  • I want to help make Fedora Workstation a great product and a gateway for average users into Fedora and FOSS
  • I want to develop a coherent story across products so that by using Workstation users have obvious ways into the other products
  • I want to help develop a strategy for Fedora Atomic

Tomas Hozza (thozza)

Introduction

• Mission Statement:
  • Make Fedora more secure and be pioneers in DNSSEC client side deployment.

• Past work summary:
  • Maintainer and contributor to many networking and DNS(SEC) related software (BIND, unbound, dnsmasq, ...).
  • Red Hat employee since 2012.
  • Co-owner of the Fedora 22 default local DNS resolver feature, Fedora 22 BIND 9.10 Change
  • Current FESCo member for approx. 1/2 year

• Future plans:
  • Support the packaging, processes and testing automation.
    • I would like to integrate a promising tool rebase-helper with Fedora upstream release monitoring to help with package rebases.
  • Ensure that Fedora is the leading distribution in enabling DNSSEC on client side.
  • Ensure no important changes are made silently without proper discussion.
  • Encourage Fedora products diversity to fit users needs.