From Fedora Project Wiki

< Development‎ | SteeringCommittee

Revision as of 03:53, 28 January 2014 by Sparks (talk | contribs) (→‎Questionnaire: Fixed header)

The nomination period is CLOSED
The nomination period ended at 23:59:59 UTC on January 13, 2014.

The following elections will take place in January 2014:

All dates and times noted are UTC time.

FESCo Elections January 2014

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 NominationsMayJune2013

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:

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 maintaining ReviewBoard. FESCo member since June 2011. Currently serving on the Fedora Server Working group.
  • Future plans: Continue to drive Fedora to become the best platform for developing exciting new technologies for the desktop and datacenter. Involve myself heavily with the Fedora Server product development and delivery.

Dennis Gilmore (dgilmore)

  • Mission Statement: Ensure Fedora is sanely deliverable, and continues to be leading edge
  • Past work summary: Former FESCo member, Former Fedora Board Member, Lead for Secondary Arches in Fedora, Fedora Release Engineer lead, Involved in Fedora since its inception. Currently serving on the Base Working Group. Member of Fedora Infrastructure. Red Hat Employee since 2008.
  • Future plans: Enable Fedora to deliver a great core, set of products, tooling and documention to enable people to come up with creative new ways to deploy and use Fedora in the real world.

Miloslav Trmač (mitr)

  • Mission Statement: Ensure Fedora products form a coordinated and well-integrated universe.
  • Past work summary: Currently FESCo and Server WG member, security architect at Red Hat. Contributor since RHL times, worked on all parts of the technology stack (from kernel through basic infrastructure to desktop and web applications). Author of the Fedora signing server.
  • Future plans:
    • With the introduction of Fedora products, make sure that they make consistent technology choices to avoid splintering the Fedora universe into incompatible subgroups and wasting effort on reimplementations.
    • More QA automation - supporting the current tool work, make it more integrated into the packaging process and increasing testing coverage.
    • Fedora is often the place where packages affected by changes other packages first interact, and handling this well is critical for achieving good user experience. To that end, I want to improve the handling of changes that affect other packages and ensuring distribution-wide consistency - while making it possible to make successful transitions faster, not slowing change down in bureaucracy.
    • I also generally favor policies that allow quick bug->fix turnaround time and allow more enhancements into released versions of Fedora.
    • Outside of FESCo my interest is in improving security of Fedora.

Marcela Mašláňová (mmaslano)

  • Mission Statement: Fedora must be usable as the development platform for all kind of developers.
  • Past work summary: FESCo member and Env and Stacks WG coordinator. I used to work mainly on maintenance of the Perl stack.
  • Future plans: Work on goals defined by Env and Stacks WG. I'd like to see more automatization in packaging and updates. I'd like to help enable software stacks for projects like Cloud or Big Data by SCL.

Toshio Kuratomi (abadger1999)

  • Mission Statement: Fedora is undergoing a transition from being simply a single Linux Distribution into a project that will create several overlapping distributions and various other platforms and technologies. I'd like the opportunity to help guide Fedora through the transition so that we can both create these new products and not abandon the good parts of the model that people have come to expect.
  • Past work summary: Infrastructure hacker. Fedora Packaging Committee member. Current FESCo member. Fedora packager from to the present. Involved in the rather ad hoc Python SIG and EPEL packaging.
  • Future plans: Currently working on how to integrate SCLs into Fedora. Looking forwards, I think we'll need something similar for docker images and openshift cartridges/gears as well.

Kyle McMartin (kylem)

  • Mission Statement: Ensure Fedora remains on the cutting edge of open source software, while providing a consistent and coherent experience to users.
  • Past work summary: Red Hat employee since 2007, Linux kernel developer, toolchain tinkerer, general OS bug fixer. Previously a Debian developer and Canonical/Ubuntu developer.
  • Future plans: Bring my experience to bear in guiding Fedora for the next few years as we transition from a mere collection of packages grouped together with little integration into a series of targeted products.


Questions are up!
The community has submitted the questions that it wants you to answer
Emails sent!
The election wrangler has sent out emails with the questions. Please contact him/her if you haven't received an email yet!
  • To achieve competitive advantage, have defined a strategy? Differentiation? Focus? Both?
  • Do you agree with, and are you committed to, the Fedora Foundations? If no, what do you believe should be changed?
  • Do you believe that it is incompatible with the Freedom foundation to allow in any way the installation of non-free software from Fedora products without an explicit and informed action on the part of the user/system administrator to allow the installation of such software?


User1 (user_1)


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


  • Question1?
    • Answer1