The following elections will take place in November/December 2012:
- Fedora Project Board (two seats)
- FESCo (Engineering) (four seats)
- FAmSCo (Ambassadors) (three seats)
- Fedora 19 Name (separate schedule from the committee elections)
All dates and times noted are UTC time.
FESCo Elections November/December 2012
These members were elected in the last elections:
- Kevin Fenzi (nirik)
- Bill Nottingham (notting)
- Peter Jones (pjones)
- Josh Boyer (jwb)
- Tomáš Mráz (t8m)
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 NominationsMayJune2012
- 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, developed the System Security Services Daemon, participant in the FreeIPA project. Currently advising the OpenLMI project and working on packaging Node.JS and its dependencies. Fedora Hosted admin maintaining ReviewBoard. Working with the OpenShift developers to host tools for use with Fedora such as Gerrit. Former FESCo member from June 2011 - 2012. Currently employed as the BaseOS Architect at Red Hat.
- Future plans:
- Continue to drive Fedora to become the best platform for developing exciting new technologies for the desktop and datacenter.
Jon Ciesla (limb)
- 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 FESCO and 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 addresses, including the Feature process, and would like to continue to contribute what experience I have to those conversations. I'm also very much interested in helping ARM achieve Primary architecture status, and have been doing a bit of work towards that goal.
Matthew Garrett (mjg59)
- Mission Statement: To help Fedora developers get their work done in such a way that we ship a distribution that benefits our users.
- Past work summary: I'm a former Red Hat employee keen on continuing to contribute to Fedora. I've worked on various power management and ACPI features, and have been leading the Secure Boot implementation that's been adopted by most significant Linux distributions. I've recently been spending time on helping with the remaining Anaconda and upgrade issues for Fedora 18.
- Future plans: FESCo exists to enable Fedora contributors to get their work done, providing that that work doesn't adversely affect other contributions or the goals of the distribution. That isn't how it's always been treated recently. I want to focus on returning FESCo to being an enabling group, while simultaneously engaging the community in discussions to fix the various infrastructural and policy flaws that stand in the way of developers.
Miloslav Trmač (mitr)
- Mission Statement: Make Fedora work better for its primary purpose as a distribution - to turn various differing upstreams into a consistent and well-integrated whole.
- Past work summary: Contributor since RHL times, worked on many things including a tcsh internals rewrite, initscripts, pyrpm, switch from MD5 to SHA-256 hashes in RPM and other places, audit work from the kernel to GUI layers, 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: Fedora is often the place where packages affected by changes other packages first interact, and handling this well is critical for fulfilling the above-mentioned primary purpose of a distribution. To that end, I plan to work on improving the Feature process, and otherwise improving 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.
Toshio Kuratomi (abadger1999)
- Mission Statement: To refine existing FESCo procedures in light of problems we've encountered.
- Past work summary: I've contributed to Fedora since the fedora.us days and was a member of FESCo during the merge of Core and Extras. Recently I've been an active member of the Fedora Infrastructure Team working on FAS, PackageDB, and general scripting and bugfixing, worked on Packaging Guidelines as a member of the Fedora Packaging Committee, and have just returned from a stint on the Board. Around alpha release, I can often be seen to step in to get python packages building or work on bugs that have hit the community's radar but aren't important enough to hit a blocker list.
- Future plans: Past FESCo's have streamlined many policies including the updates policy, a fast track for nonresponsive maintainers, and how FPC guidelines are approved. The current and next FESCo are likely going to be tackling an update of the Feature Process. There's been a lot of work around this already. Many packagers have contributed to the Fixing_features wiki page. FESCo has been discussing issues on the Refining Features ticket. I'd like to help organize the identified problems and suggested solutions and incrementally improve pieces of the policy. If we finish that work, it may be time to take another look at improving the non-responsive maintainer policy.
Marcela Mašláňová (mmaslano)
- Mission Statement: Fedora should be opened for new projects, but we need to work more on inclusion of changes. Features or changes of default shouldn't lead to breakage of rest of the system.
- Past work summary: Red Hat employee since 2006. I started as a maintainer of small utilities in Base group and become a Perl maintainer. Currently, I'm working as a supervisor of Languages group. I have almost finished second term in FESCo. My current project is Software Collections, which are able to provide more versions of the same software in a single distribution release.
- Future plans: Fedora should provide environment stable enough for development of new features. I'd like to work in FESCo on review of new features and help to communicate between group of developers so the lack of communication does not bring surprises late in the development cycle of release.
Martin Sivák (msivak)
- Mission Statement: Make sure the distribution stays modular and adaptable to the needs of many different user groups
- Past work summary: I have been a linux user since 1999, starting with Red Hat 7.1 and moving through different distributions including Linux From Scratch to the current Fedora 17. I also co-started a local annual linux conference for beginners and intermediate users in 2006 and have led the organization team for the last 5 years. Since 2007 I have also worked for Red Hat in Brno, mostly focusing on the anaconda internals, text mode and driver loading subsystems.
- Future plans: We have some places in the distribution which affect very large number of other packages and environments. Some of those were even adopted by other distributions and people are working on making the learning curve for converts smooth. Unfortunately, sometimes we forget the motto of one tool doing one thing, but doing it properly. When that happens, we loose the ability to replace packages easily, integrate them in different environments and also to test them in isolation. But all those points are important from the engineering and QA point of view and make it easier for other desktop environments and distributions to integrate the tools. So I would like to help tweak the Feature process to take this into account and work with the community to make sure Fedora parts are more easily reusable by others.