From Fedora Project Wiki

Put your nominations here (keep them in alphabetic order please).

Candidates

Josh Boyer

  • Goal Statement: Leverage the expertise across the Fedora contributor base to create a productive and friendly environment for all contributors. Continue working towards a complete secondary architecture solution.
  • Past work summary: I own a small number of packages in Fedora, however packaging hasn't been my primary focus. Instead I have been working on Release Engineering, and PowerPC support. I've also been on FESCo for the past two terms.
  • Future Plans: Continue to ensure Fedora works well on PowerPC and other secondary architectures, and aid again in Release Engineering as I can. Look for ways to bring new contributors into Fedora.
  • Other: I have no ninjas, nor superpowers. I don't have campaign finance managers, or TV commercials either. If you have a question on where I stand on an issue, please feel free to ask me.

Steve Dickson

  • Mission Statement: My goal is to continue to make Fedora the best development platform for both kernel and user level development. I would also like to see Fedora continue to be on the leading edge of technology with emphases on put more energy into automating testing procedures to ensure Fedora 'right-out-of-box' quality.
  • Past work summary: I'm one of Red Hat's NFS maintainers. I'm the upstream and Fedora maintainer of a number of packages include nfs-utils. I served on the Fedora Board for the last two releases.
  • Future Plans: Continue to make NFS the best it can be, especially version 4 which includes making version 4 the default, integrating Secure NFS with new project like OpenIPA. Finally, support the community's needs in whatever it takes to keep Fedora as one of the top development platforms.

Kevin Fenzi

  • Mission Statement: My current goal is to try and revamp the community support that Fedora offers, starting with IRC support. I also hope to work more on lowering barriers to entry in packaging and keep high quality standards. I'd like to drive more automated QA/packaging checks in the next development cycle.
  • Past work summary: I maintain the Xfce packages for Fedora, along with a number of others. I process most of the packagers CVS requests. I try and help out on the #fedora channel assisting end users and maintaining order. I'm on the security team, where I try and make sure the EPEL packages are kept up to date with security issues and pushed out in a timely manner. I run monthly checks of sources files from packages in CVS. I maintain x86_64 and ppc32 machines for packages to test/build on.
  • Future Plans: Revamp support, starting with IRC, and moving on to mailing lists and forums. Try and improve package quality with more automated checking. Get Packagers access to test machines for all platforms so they can build/test/fix things on all arches.

Dennis Gilmore

  • Mission Statement : My goal is to continue to be a voice for infastructure, Secondary Arches and OLPC, Making sure that where possible everything needed to run fedora on a day to day basis is available and done. Try to ensure that each step Fedora makes is a step forward.
  • Past work summary : Maintain Extras for Aurora SPARC Linux, maintain a small handful of packages, buildsystem maintenance. I have done alot of work in infrastructure making sure that servers are up and running. Implemented EPEL buildsys and drove the initial idea forward. FESCo member, Fedora Board member and past EPEL steering committie member.
  • Future Plans : Continue work on Secondary Arches, Build system improvements, Making a better experience for maintainers in anyway I can. I also have an interest in Security.

Karsten Hopp

  • Mission Statement: Some of you may already know me from my bugzilla reports about package rebuild problems and know that I'm working on better package quality. I'll take this to the next level and formulate and discuss new guidelines to prevent the most common errors.
  • Past work summary: I've joined Red Hat in 1998 when Red Hat aquired the German Linux distributor 'delix' and I've been working on RHEL and Fedora since their inceptions. I've written most of the initial mainframe support of anaconda and still maintain one of our mainframe partitions. I have done numerous mass rebuilds of RHEL and Fedora and filed lots of bugzillas or fixed packages myself when I found bugs.
  • Future plans: Develop a framework for distributed mass rebuilds and scripts for sanity checks between the rebuilt and the original packages. These rebuilds often have different sets of installed packages and can't be done with koji (p.e. rebuilds in a full install chroot vs. the minimum installs done in mock). I also plan to get involvedin Fedora on secondary archs (i.e. mainframe)

Jon Masters

  • Goal Statement: Help to keep Fedora at the highest of standards, while using the opportunity to get more involved in the Fedora project, and provide some new blood. I also want to continue to work on lower level pieces of infrastructure, and would like to serve as a liaison between the Fedora Project and Red Hat's RHEL - as someone who actively works on both I feel that I can better help both sides work together toward common solutions. That doesn't mean trying to change Fedora to benefit RHEL :)
  • Past work summary: I own a few packages in Fedora, including module-init-tools. I've been a Linux user and developer since around 1995/1996 and have switched between Red Hat Linux, Slackware, Debian, and Ubuntu (and others too). I've been heavily involved in embedded systems development, and have written books about Linux development, and embedded systems. I actively follow other Linux communities, test releases, and take an interest in some of the more ugly discussions - from kmod packaging to multilib. I also work heavily on RHEL5 and on the RHEL Real Time kernel.
  • Future Plans: Continue to work on the bits I have in the past. Try to get more involved in discussions, testing, etc. A couple of big things I would like to achieve: 1). Testing. I would really like to promote updates-testing and focus on quality, although the current bar is already pretty damn good. 2). Draw new interest and get more community members involved (there's a well known Fedora "mainstay", but newcomers must feel welcome too). This means trying to be as inclusive as possible in terms of listening to community input rather than just who shouts the loudest.
  • Other: I'm variously opinionated on quite a few topics, feel free to email me and grill me or read through my posts, website, etc. :)

Bill Nottingham

  • Mission Statement: I plan to represent the Fedora community in FESCo with an eye towards maintaining the quality and standards of the Fedora distribution, including features, testing, release engineering, and so on.
  • Past work summary : Red Hat employee since 1998, developer on Red Hat Linux since 5.1, Fedora contributor since its inception, FESCo member, Fedora board member, Release engineering team member, and assorted other roles.
  • Future plans : Continue to make Fedora the best freely available distribution anywhere.

Jon Stanley

  • Mission Statement: My mission as a member of FESCo will be to be a voice of the QA and bug triage functions within Fedora to FESCo. These are areas which require representation, due to their needing to be a close relationship with the maintainer community. This includes very active participation in the feature process, ensuring that features are in testable/final states by required milestones.
  • Past work summary: Revitalized the bug triage effort during the Fedora 9 cycle, and maintain a (very) small amount of packages. I've done a lot of work in release QA, as well, helping to ensure that Fedora is the world-class operating system that it deserves to be.
  • Future plans: Continue work on bug triage and QA, and make contributing to these projects the rewarding experience that it should be. Oversight of the feature process and various SIG's as required, however, I much prefer a hands-off approach unless intervention is required. At that time, intervention should be swift and with the goal of resolving the issues as quickly as possible.

Jarod Wilson

  • Mission Statement: Many Red Hat Enterprise Linux folks still don't understand Fedora entirely well, and need educating. And vice versa sometimes. I intend to provide something of a bridge between some of Red Hat's internal RHEL people and the Fedora world (particularly as it relates to the kernel). I've also got a vested interest in aiding and abetting the success of Fedora on the secondary arches, particularly those that are supported RHEL arches, since if Fedora runs on 'em, RHEL6 ought to also...
  • Past work summary: software engineer in Red Hat's enterprise kernel group (since early 2006), previously an engineer at now-defunct Linux Networx, long-time Fedora user/developer, maintainer of a number of Fedora packages, and all-around nice guy. Honest.
  • Future plans: Keep working on making the Fedora kernel better and better (spec file enhancements, firewire subsystem, etc), which of course trickles back into making the RHEL kernel better too. Help get more RHEL engineers actively involved in Fedora.

David Woodhouse

  • Mission Statement: Ensure that Fedora continues to be a portable, high-quality distribution, suitable for developers and new users alike, across all architectures.
  • Past work summary: Mostly a kernel hacker, although I maintain a bunch of userspace packages and have done a lot of work with OLPC. FESCo member since 2007. Built Extras and Livna for Fedora/PPC, given out accounts on test boxen and helped Fedora/PPC get to the point where it could be a primary release in Fedora Core 4.
  • Future Plans: Work to bring more architectures into the Fedora camp and make them as viable as possible. Help to do anything possible to ensure OLPC works, and continues to find Fedora useful. Refrain from promoting an attitude of violence except where absolutely necessary. World domination.

Nominations

If accepted by nominee, please move information to the Candidates section

Foo

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

Nominations in case there are not enough candidates in the previous section

ChristianIseli

  • Mission Statement : I'm a firm believer in the KISS principle, think that common sense should trump, and like to have as many things open as possible.
  • Past work summary : I maintain 7 packages, seat in FESCo, and try to keep the ["PackageMaintainers/PackageStatus"] page up to date. I've been known to participate in mass rebuilds, mass BZ ticket filing, and otherwise make a nuisance of myself on occasions.
  • Future Plans : I'll continue to keep an eye on the review process, making sure all packages can be easily traced from review submission to retirement. I also like to automate things where possible. I'd like Fedora to become the de-facto source of high quality packages that other, slower moving distros can use to build their stuff on. I'd like Fedora to stay on the bleeding edge, to be the main interface between upstream project developers and usable packages in a coherent distribution.

WarrenTogami

  • I maintain many packages in Fedora, FESCO member for many years, and also member of Fedora Release Engineering. I spend a lot of time working on LTSP for Fedora.

History

Watch nominations for older elections:

Retrieved from "https://fedoraproject.org/w/index.php?title=Extras/SteeringCommittee/Nominations&oldid=39161"