For the last election, see Development/SteeringCommittee/NominationsJune2011
Person Name (IRC nickname)
- Mission Statement:
- Past work summary:
- Future plans:
Justin 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: My original involvement in the Fedora project was working on the port to x86_64 for FC1. More recently I have been focused on virtualization within Fedora and the Cloud SIG.
- Future plans: Strive to make Fedora the best freely available distribution. Focus on improving improving the developer/tester interaction, the feature process, and general communication with the community.
Jon Ciesla (limburgher)
- Mission Statement: To further the goals of the project and Free Software in general by helping enable contributors to bring the highest quality and most diverse collection of software to the distribution. I'm fully committed to the goals of Free Software, for ideological, but also primarily technical reasons.
- Past work summary: I've been a Fedora user since RHL 7.1, and an active packager since 2007, as well as a sponsor and member of the FPC. I initially focused on games and php applications, but have expanded to other things over time. I also encounter and deal with many of the issues we encounter as a project in the course of my day job.
- Future plans: Ideally, I'd like to find ways to encourage and educate new contributors. I've sponsored a few new packagers, but would like to help shorten the time from first interest to active packager, and can only do so much on my own. I also have ideas and opinions on many areas FESCO address, and would like to contribute what experience I have to those conversations.
Marcela Mašláňová (mmaslano)
- Mission statement: Fedora should be a solid platform for development. I'd like to see FESCo as strict reviewer of new features, which can be disruptive for the distribution. FESCo should guide and help with global changes. But it shouldn't create new processes, it should rather review old ones.
- Past work summary: Red Hat employee since 2006, maintaining about 150 packages, mainly Perl modules.
- Future plans: Currently, I'm working on Dynamic Software Collection, which could provide more versions of software in the distribution. I'd like to co-operate on creation of better scripts and guidelines for (mass-)rebuilds.
Matthew Garrett (mjg59)
- Mission statement: Fedora needs to engage in aggressive development in order to push the Linux platform forward, but simultaneously produce usable and stable releases in order to get free software into the hands of our users. As part of FESCo, I will continue to push for developer freedom in the development path while continuing to work on ensuring that our stable updates are both timely and stable.
- Past work summary I've been working on improving Linux hardware and laptop support since 2004. Right now I'm employed by Red Hat to improve Linux power management and firmware (ACPI and UEFI) support.
- Future plans: Continuing to work on making sure that Fedora can take full advantage of hardware features, from power management to firmware updates.
Miloslav Trmač (mitr)
- Mission Statement: Make Fedora a more attractive/fun distribution for developers to use and work on.
- Past work summary: Contributor since RHL times, worked on many things including tcsh i18n/signal handling rewrite, initscripts, pyrpm, switch from MD5 to SHA-256 hashes in RPM and other places, system-config-audit, audit-viewer, TTY input auditing, volume_key, encrypted disk support in libvirt, kernel's crypto interface, and the Fedora signing server. Used to be a heavy-duty translator into Czech.
- Future plans: Linux is primarily shaped by things that happen upstream. In the limited capacity that FESCo has to influence it, I want to generally favor policies that allow quick bug->fix turnaround time, allow more enhancements into released versions of Fedora, and ask for clear and time-definite migration paths when subsystem replacements are proposed (at least within the default spin). Outside of FESCo my interest is in improving security of Fedora as a whole, without requiring manual work for each individual package.