Put your nominations here (keep them in alphabetical order by surname please).
There are 4 seats open in this election. The seats open are currently held by Jon Stanley, Dan Horák, Jarod Wilson, and David Woodhouse (Josh Boyer's original seat).
- 1 Nominees
- 2 Template
- 3 History
Justin M. Forbes (jforbes)
- Mission Statement: Work 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 available.
Matthew Garrett (mjg59)
- Mission Statement: Help encourage Fedora's development into a world-leading operating system, focusing on ensuring that we not only satisfy our existing users but can gain new users purely on merit.
- Past work summary: I've only been involved in the Fedora project since F9, but before then I've been a Debian developer and was the community member on the Ubuntu Technical Board. I work on power management across a wide range of Fedora, including the kernel, X server and desktop, and also focus on improving laptop support - I maintain several laptop drivers in the kernel and have squashed a number of ACPI issues.
- Future plans: From a technical view, driving down Fedora's power consumption until it's below that of any OS with equivalent functionality. From a FESCO point of view, doing what I can to aid the work Fedora needs doing most. FESCO should exist to facilitate, not to block.
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 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 extra work, or in duplication of effort. I'll try to guide our policy decisions to put the power and responsibility in developers hands rather than requiring FESCo's intervention and participation at every level, just as I have when proposing policies in the past.
- 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, 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.
- 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'd like 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 wasted effort.
Richard June (rjune)
- Mission Statement: I want to see Fedora be a very usable and approachable OS. I want things to either work or give an indication why they failed. I want to see gaps in utilities filled.
- Past work summary: Originally involved with fedora at FC1, I maintained a fedora-extras + livna compatible repository for Fedora 2, 3, and 4. Additionally I have written config-dhcpd, a utility meant to fill a hole in the system-config-* tools.
- Future plans: Add management utility for LDAP and add LDAP support for existing system-config tools, work on ironing out some of the "paper cut" bugs that don't really impair functionality, but annoy users.
Robert Scheck (rsc)
- Mission Statement: Making Fedora the world dominating Linux distribution ;-) Seriously, I would try to be a real representative of the Fedora community at FESCo - and getting points and opinions from the community better into FESCo and especially into votings and decisions. Also I would try to kick maintainers via policies to get them handling their bug reports better and faster and especially if upstream is the same person as downstream and all needed information are already provided but not handled.
- Past work summary: I'm using Linux since Red Hat Linux 6.2, thus Fedora from the very first beginning. I started contributing with Red Hat Linux 9; later in Fedora Core and Extras days, I got packager and with the Core and Extras merge, I got an ambassador. Today I'm maintaining about 60 packages on all active Fedora and EPEL branches (if technically possible). I'm supporting the websites team as well as the German translation team, too. Beside of that, I try to be a good mentor for new Fedora ambassadors and packagers and if there's still time, I use my provenpackager status to give a bit love to broken packages.
- Future plans: Making the Fedora world for users better. Fedora needs to get more usable on server systems (without X and the dependency bloats) and FESCo needs a bit more transparency than in the past (e.g. regarding the missing meeting minutes).
Jon Stanley (jds2001)
- Mission Statement Making Fedora the world class distribution that it deserves to be. Some immediate term goals include developing a policy and implementation strategy for "updates discipline" - the concept that while not impeding the rapid progress that Fedora is known for, we should also not push potentially destabilizing updates into stable Fedora releases. I also plan to play a significant role in EPEL6 whenever that comes around :). I also plan to be a voice of Infrastructure in FESCo. Also, with (at current) no other current FESCo members running for re-election, I would also bring long term stability and institutional knowledge to FESCo.
- Past work sunmary: Served on FESCo for the last 1.5 years, for the past year as chair. I maintain approximately 19 packages in Fedora, and maintain all fo them in the EPEL branch(es) that they build on and/or apply to. I am also active in Fedora Infrastructure, and am a sponsor for two functions within the Infrastructure team. I am also a Ambassador representing Fedora at various events throughout the United States.
- Future Plans: See the mission statement really, but I cannot overstate the importance of discipline in stable Fedora updates. As part of the recent "What is Fedora" discussion, for what we have defined our target audience as (and pretty much common sense), we simply cannot have a "yum update" deliver a broken system to the user, where that system was previously working.
Christoph Wickert (cwickert)
- Mission Statement: Improve packaging quality and enforce higher standards for better cross desktop interoperability. Try to reduce the dependency bloat to make sure Fedora does not become too fat, so it still can be used on older or smaller hardware like Netbooks or the XO without too much pain.
- Past work summary: Fedora's Handyman: Long time contributor, packager, sponsor and ambassador. Currently maintaining all Xfce Goodies, the Xfce core packages (together with Kevin Fenzi), the LXDE desktop (official F-10 feature) and some other stuff (> 100 packages). In the F12 development cycle I did the Xfce and LXDE Spin and helped Gerd with the Rakudo Feature. Did some artwork (Nodoka for XFWM4, Sugar for XFWM4 and OpenBox). Attended several events and helped organizing them. I'm also contributing to LXDE and OLPC upstream.
- Future plans: Improve communication between the different bodies in the project and make decision-finding more transparent to all contributors. Take care of new contributors and support them wherever needed. Continue to promote Fedora as an ambassador and by doing one event every month and by giving more talks. Encourage cooperation with the upstream projects I'm supporting.
Will Woods (wwoods)
- Mission Statement: FESCo should make policies and decisions that make the distribution more stable and easier to use, in order to satisfy our current users and help our developers continue to advance the state of Open Source Software as a whole.
- Past work summary: I've worked on Fedora since FC4, originally as QA Lead and now as more of a QA Architect, working primarily on the AutoQA project. I have other utility roles - rel-eng team member, QA advisor to FESCo and the Board, etc - and maintain a handful of packages, including PreUpgrade, which I co-authored with skvidal and timlau.
- Future plans: Build out AutoQA to help developers maintain and test their packages (and make things more stable for all our users). Work on a simpler (and faster) alternative to bugzilla, so users and developers spend less time dealing with bug reports. Improve our bug reporting tools so the reports we do get are complete and useful. Clarify and streamline the Feature process. Find ways to make updates more reliable and less frequent. Find ways to give SIGs more autonomy and Spins more control over their content.
Person Name (IRC nickname)
- Mission Statement:
- Past work summary:
- Future plans:
Watch nominations for older elections: