From Fedora Project Wiki
Nominations are closed.
The nomination period ended on November 7th.

In the November 2010 election, there are 4 seats open. The seats open are currently held by: Adam Jackson (ajax), Christoph Wickert (cwickert), Peter Jones (pjones), and Matthew Garrett (mjg59).

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.
  • Future plans: Strive to make Fedora the best freely available distribution.

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: Work towards enforcing Fedora's Stable Updates vision and facilitate tighter integration between popular client applications and the desktop.

Matthew Garrett (mjg59)

  • Mission Statement: Help ensure that Fedora is a stable platform that can be relied upon by users, while simultaneously ensuring that developers are able to make Fedora into whatever they want.
  • Past work summary: I'm heavily involved in upstream kernel work, mostly on power management but also the interaction between the kernel and userspace. In Fedora terms I concentrate on power management and laptop bugs in the kernel and testing of advanced power management features and the appropriate userspace support. I've been on FESCo for the past year and have contributed to the stable update policy work. Before Fedora I sat on the Ubuntu technical board, and I've also been a Debian developer.
  • Future plans: Now that we have a more solid idea of our update policy implemented, I'd like to focus on helping those that want a more bleeding edge system be able to get one. It's much easier to build support for unstable updates on top of a stable base than the other way around. I also want to help ensure that technical barriers to entry are low, and that anyone with something to contribute to Fedora can do so.

Adam Jackson (ajax)

  • Mission Statement: Fedora has exceptionally many and exceptionally talented contributors. Its continued success depends on improving the processes and tools used by those contributors to make their continued innovation as easy as possible, and on making it ever easier for others to consume what Fedora produces.
  • Past work summary: X developer since X.Org 6.8 or so. X maintainer (well, one of many) for Fedora since Fedora Core 6. Drive-by contributions and bugfixes to Gnome, Mesa, rpm, anaconda, the kernel, and whatever else happens to be in my way. X.Org Foundation board member for the past two years, and standing for election again this year.
  • Future plans: Within the context of FESCo: see the mission statement, really. Identify and name the bugs in our tools and processes, evaluate and recommend solutions, and clear the path for the people who implement them.

Peter Jones (pjones)

  • 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 streamline our processes for developers, and to avoid processes that result in unnecessary work, or in duplication of effort. 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 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. 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 in anaconda as well as supporting various storage technologies in anaconda and dracut. 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.

Marcela Mašláňová (mmaslano)

  • Mission Statement: Fedora usable on server, support Spins and Features.
  • Past work summary: Red Hat employee since 2006, maintaining about 150 packages, mainly perl modules.
  • Future plans: Work with Server SIG on server spin. Make contributors life easier by policy/infrastructure.

David Ramsey (dramsey)

  • Mission Statement: Offer my technical assistance for Fedora's advancement as well as future development.
  • Past work summary: Was a system administrator for a few thousand users and conducted system integration.
  • Future plans: Create and manage a variety of virtualized systems as well as develop SELinux-based systems.

Christoph Wickert (cwickert)

  • Mission Statement: Lets get back to the good ol' days, where a contributor's life in Fedora was easy because there was trust and good will. I'm not saying that all recent changes are bad (and as FESCo member I'm responsible for some of them), but in some areas it has become too much red tape to work efficiently. Give the community the control (back) and get all groups the same resources.
  • Past work summary: Senior Engineer at Kolab Systems, Maintainer and release manager of the Kolab groupware server. Long time Fedora contributor, proven packager, sponsor and ambassador. Currently maintaining the LXDE desktop and Spin, Xfce and some more stuff, all together ~ 150 packages. Member of FESCo since Fedora 12.
  • Future plans: 1. Work on the "updates-features" repository implementation for the users who want new versions during a Fedora release. 2. Improve QA to make Fedora more user friendly. 3. Make anaconda work well for all desktop environments with a reasonable package selection. 4. Bring the Kolab groupware server in Fedora.