From Fedora Project Wiki
No edit summary
No edit summary
(28 intermediate revisions by 13 users not shown)
Line 1: Line 1:
<!--{{admon/important|The nomination period is CLOSED. The nomination period ended at 23:59:59 UTC on May 15, 2012.}}-->
{{admon/important|The nomination period is CLOSED|The nomination period ended at 23:59:59 UTC on May 25, 2013.}}
<!--{{admon/important|The nomination period has not yet begun. Please wait for the elections announcement}}-->
<!--{{admon/important|The nomination period has not yet begun. Please wait for the elections announcement}}-->
{{admon/important|We're OPEN!|The nomination period is in progress!}}
<!--{{admon/important|We're OPEN!|The nomination period is in progress!}}-->
<!--{{admon/tip | VOTE FOR YOUR FAVORITE CANDIDATES. | Fedora contributors can elect FESCo at https://admin.fedoraproject.org/voting/about/fesco-december2012.-->
<!--<br />DEADLINE: Dec. 9, 23:59:59 UTC}}-->


The following [[Elections|elections]] will take place in May/June 2013:


The following [[Elections|elections]] will take place in November/December 2012:
* [[Board/Elections/Nominations|Fedora Project Board]] (three seats)
 
* [[Development/SteeringCommittee/Nominations|FESCo (Engineering)]] (five seats)
* [[Board/Elections/Nominations|Fedora Project Board]] (two seats)
* [[Development/SteeringCommittee/Nominations|FESCo (Engineering)]] (four seats)
* [[FAmSCo_nominations|FAmSCo (Ambassadors)]] (three seats)
* [[FAmSCo_nominations|FAmSCo (Ambassadors)]] (three seats)
* [[Name suggestions for Fedora 19|Fedora 19 Name]] (separate schedule from the committee elections)
* [[Name suggestions for Fedora 19|Fedora 19 Name]] (separate schedule from the committee elections)
Line 13: Line 14:
All dates and times noted are UTC time.
All dates and times noted are UTC time.


= FESCo Elections November/December 2012 =
= FESCo Elections May/June 2013 =


These members were elected in the [https://admin.fedoraproject.org/voting/results/fescof18? last elections]:
These members were elected in the [https://admin.fedoraproject.org/voting/results/fescof19? last elections]:
* [[User:Toshio|Toshio Kuratomi]] (abadger1999)
* [[Miloslav Trmač]] (mitr)
* [[User:mmaslano|Marcela Mašláňová]] (mmaslano)
* [[User:sgallagh|Stephen Gallagher]] (sgallagh)
 
 
As per the [[FESCo_election_policy|FESCo election policy]], the following finish their terms, and the seats are up for re-election:


* [[User:Kevin| Kevin Fenzi]] (nirik)
* [[User:Kevin| Kevin Fenzi]] (nirik)
Line 22: Line 30:
* [[User:jwboyer|Josh Boyer]] (jwb)
* [[User:jwboyer|Josh Boyer]] (jwb)
* [[User:Tmraz|Tomáš Mráz]] (t8m)
* [[User:Tmraz|Tomáš Mráz]] (t8m)
As per the [[FESCo_election_policy|FESCo election policy]], the following finish their terms, and the seats are up for re-election:
* [[User:Mitr| Miloslav Trmač]] (mitr)
* [[User:Limb| Jon Ciesla]] (limburgher)
* [[User:Mjg59| Matthew Garrett]] (mjg59)
* [[User:Mmaslano|Marcela Mašláňová]] (mmaslano)


More information at the FESCo [[Fedora_Engineering_Steering_Committee|wiki page]].
More information at the FESCo [[Fedora_Engineering_Steering_Committee|wiki page]].
Line 34: Line 35:
<!--{{admon/important|The nomination period is CLOSED. The nomination period ended at 23:59:59 UTC on May 15, 2012.}}-->
<!--{{admon/important|The nomination period is CLOSED. The nomination period ended at 23:59:59 UTC on May 15, 2012.}}-->


For the last election, see [https://fedoraproject.org/w/index.php?title=Development/SteeringCommittee/Nominations&oldid=290360 NominationsMayJune2011]
For the last election, see [https://fedoraproject.org/w/index.php?title=Development/SteeringCommittee/Nominations&oldid=290360 NominationsMayJune2012]


{{admon/note|Eligible Voters|Voting eligibility is determined by a community member's Fedora Account System ([https://admin.fedoraproject.org/accounts/ FAS]) memberships.<br/> <br/>To vote for [[Fedora_Engineering_Steering_Committee|FESCo]] you must have cla_done + one other "non-cla" group in FAS.}}
{{admon/note|Eligible Voters|Voting eligibility is determined by a community member's Fedora Account System ([https://admin.fedoraproject.org/accounts/ FAS]) memberships.<br/> <br/>To vote for [[Fedora_Engineering_Steering_Committee|FESCo]] you must have cla_done + one other "non-cla" group in FAS.}}
Line 44: Line 45:
* '''Past work summary:'''
* '''Past work summary:'''
* '''Future plans:'''
* '''Future plans:'''


=== Questionnaire ===
=== Questionnaire ===
<!--The community has submitted the questions that it wants you to answer. The list of questions is here: [[F18_elections_questionnaire#Fedora_Engineering_Steering_Committee_.28FESCo.29|F18_elections_questionnaire#Fedora_Engineering_Steering_Committee_.28FESCo.29]] -->
<!--[[F18_elections_questionnaire#Fedora_Engineering_Steering_Committee_.28FESCo.29|F18_elections_questionnaire#Fedora_Engineering_Steering_Committee_.28FESCo.29]] -->
 
{{admon/warning|CLOSED|The questions have not been posted. Please wait for the questionnaire wrangler to contact you!}}
<!--{{admon/important|Questions are up!|The community has submitted the questions that it wants you to answer}}-->
<!--{{admon/important|Emails sent!|The election wrangler has sent out emails with the questions. Please contact him/her if you haven't received an email yet!}}-->
<!--{{admon/warning|Candiates, don't post your answers yet|Once the questionnaire period is over, the Elections Wrangler will collect the answers and post them at the same time. This attempts to make things more even and fair for candidates to be open with their answers and not copy from earlier responses.}}-->
<!--{{admon/warning|CLOSED|The answering period is now closed (after November 18 2359 UTC). Received responses are below:}}-->
 
* Question 1
= Candidates =
 
== [[User:user1|User1]] (user_1) ==
 
=== Introduction ===
 
* '''Mission Statement:'''
**
 
* '''Past work summary:'''
**
 
* '''Future plans:'''
**
 
=== Questionnaire ===
* Question1?
** Answer1
 
== [[User:kevin|Kevin Fenzi]] (kevin) ==
 
=== Introduction ===
 
I have long been a Fedora contibutor and I'd like to continue to help guide Fedora's Technical decisions.
 
* '''Mission Statement:'''
 
To continue to guide techincal decisions in Fedora and help others get done the things that help our community.
 
* '''Past work summary:'''
 
Package maintainer since the extras days: https://admin.fedoraproject.org/pkgdb/users/packages/kevin
 
I co-maintain the Xfce desktop packages.
 
Work with release engineering
 
I have served on FESCo for a long time.
 
Employed as Fedora Infrastructure lead to keep all our various infrastructure going.
 
Lots of other things...  
 
* '''Future plans:'''
 
Finish process changes to get <strike>Features</strike> moved to Changes and help streamline tracking.  
 
Clean up and modernize some of our policies, especially non responsive maintainers policy.
 
== [[User:notting|Bill Nottingham]] (notting) ==


{{admon/warning|CLOSED The questions have not been posted. Please wait for the questionnaire wrangler to contact you!}}
=== Introduction ===


{{admon/warning|Candiates, don't post your answers yet|Once the questionnaire period is over, the Elections Wrangler will collect the answers and post them at the same time. This attempts to make things more even and fair for candidates to be open with their answers and not copy from earlier responses.}}
* '''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, stability, release engineering, and so on.


= Candidates =
* '''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. Work with those that show up to make changes, as, realistically, FESCo does not have a significant amount of resources to direct.
 
== [[User:Pjones|Peter Jones]] (pjones) ==
 
=== Introduction ===
 
* '''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 ensure that our processes for developers are as simple as possible, and to avoid processes that result in unnecessary work, or in duplication of effort, as we form new rules for change management in Fedora.  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 since 1998 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 of Fedora's packages for booty, cdparanoia, dumpet, gnu-efi, grub, grub2, grubby, 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 also represent Red Hat and Fedora on the UEFI Specification Working Group. 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 throughout Fedora.  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, especially as we revamp the Feature process.


== [[User:Sgallagh|Stephen Gallagher]] (sgallagh) ==
== [[User:tmraz|Tomáš Mráz]] (t8m) ==


=== Introduction ===
=== Introduction ===


* '''Mission Statement:'''
* '''Mission Statement:'''
** Make Fedora THE platform for rapidly developing the next generation of free, open-source software.
 
Keeping Fedora as an usable and good quality operating system for running server and desktop applications.


* '''Past work summary:'''
* '''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.
 
I've been Red Hat employee and Fedora contributor for more than eight years working on packages related to security (PAM, OpenSSL, libgcrypt, GNUTLS, ...) in both Fedora and Red Hat Enterprise Linux. I am one of the upstream maintainers of PAM. I was FESCo member for the past two years.


* '''Future plans:'''
* '''Future plans:'''
** Continue to drive Fedora to become the best platform for developing exciting new technologies for the desktop and datacenter.


== [[User:Limb|Jon Ciesla]] (limb) ==
Apart from trying to adhere in my FESCo work to the mission statement above I'd like to help with implementation of the
new change process and the Fedora revamp proposal. I'd also like to bring at least slightly more democracy into the FPC membership process.
 
== [[User:mattdm|Matthew Miller]] (mattdm) ==


=== Introduction ===
=== Introduction ===


* '''Mission Statement:'''
** To see the Fedora distribution become more widely used as a platform, with modular layers of enabling technology all within the wider circle of the Fedora community.


* '''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:'''
* '''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.
** I've worked with Fedora since the beginning, as a community member and in my various roles as sysadmin and systems architect at Boston University and Harvard. (At BU, I helped host the very first FUDCons.) I've maintained a number of small packages for a long time. I was hired by Red Hat last year to work on Fedora Cloud, and have been working with others in the Cloud SIG to add polish to our Cloud images. I'm also on the Minimal Core SIG, which I care about both for the cloud images and because changes there ripple out and affect everyone. I'm often active on the mailing lists, and while I sometimes have strong opinions, I know I'm not always right and therefore try very hard to listen to all the different viewpoints.
* '''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.


* '''Future plans:'''
** I have a somewhat active vision for a Fedora project, centered around a base platform and with greater latitude for SIGs to solve problems within their areas. I'd like to see a more carefully managed (but not stagnant!) core OS, while allowing other layers to be less perfect when perfection is getting in their way — yet still hold those layers to standards agreed on by the Fedora community. Without both of these things, we risk becoming irrelevant: either beautiful but rarely used, or completely marginalized as we're passed by. Fedora is the best enthusiast distribution, and it can ''also'' be the best platform for development, the best cloud environment, and the base for a polished end-user experience.
== [[User:jwboyer|Josh Boyer]] (jwb) ==


== [[Miloslav Trmač]] (mitr) ==
=== Introduction ===
=== Introduction ===


* '''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.
* '''Mission Statement:'''
* '''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.
** To ensure Fedora remains a high quality, leading edge distribution with a variety of uses.
* '''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 distributionTo 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 bureaucracyI 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.
 
* '''Past work summary:'''
** I have been a Fedora user since its inception, and a Fedora contributor since around Fedora Core 4.  In the past I've held positions on the Fedora Board and Fedora rel-eng teams.  I was also part of the PowerPC secondary architecture effort.  I've been on FESCo off and on since 2006.  I am currently one of the three Fedora kernel maintainers, and I am a FESCo member running for re-election.
 
* '''Future plans:'''
** Continue to let developers and contributors accomplish what they need with a minimum amount of process and overheadHelp with the new change process as it evolvesContinue to look at the distro as a whole with an eye on improving the usability and function for a variety of targets.


== [[User:toshio|Toshio Kuratomi]] (abadger1999) ==
== [[User:kalev|Kalev Lember]] (kalev) ==


=== Introduction ===
=== Introduction ===


* '''Mission Statement:'''
* '''Mission Statement:'''
** Make sure Fedora stays relevant for both end users and developers.


* '''Past work summary:''' I've contributed to Fedora since the fedora.us days and was a member of the second FESCo. Recently I've been an active member of the Fedora Infrastructure Team, 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 this or that bug that's hit the community's radar but hasn't made it's way onto any blocker lists.
* '''Past work summary:'''
** Fedora contributor for over 4 years, provenpackager and packager sponsor.
** Co-handling the GNOME mass builds in Fedora.
** Contributor to upstream GNOME.
** Involved with the Fedora MinGW SIG since its beginning.


* '''Future plans:'''
* '''Future plans:'''
** Try to make Rawhide a more usable platform for day-to-day use.
** Fine tune the Branched release schedule and release engineering workflow to minimize rawhide bitrot. Right now Branched gets a lot of undivided attention for nearly 4 months before the release, and developers are off rawhide during that time.
** Get Fedora back on track with its 6-month schedule, synced with upstreams that release every 6 months.

Revision as of 03:26, 26 May 2013

Important.png
The nomination period is CLOSED
The nomination period ended at 23:59:59 UTC on May 25, 2013.

The following elections will take place in May/June 2013:

All dates and times noted are UTC time.

FESCo Elections May/June 2013

These members were elected in the last elections:


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

Note.png
Eligible Voters
Voting eligibility is determined by a community member's Fedora Account System (FAS) memberships.

To vote for FESCo you must have cla_done + one other "non-cla" group in FAS.

Candidate template

Introductions

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


Questionnaire

Warning.png
CLOSED
The questions have not been posted. Please wait for the questionnaire wrangler to contact you!
  • Question 1

Candidates

User1 (user_1)

Introduction

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

Questionnaire

  • Question1?
    • Answer1

Kevin Fenzi (kevin)

Introduction

I have long been a Fedora contibutor and I'd like to continue to help guide Fedora's Technical decisions.

  • Mission Statement:

To continue to guide techincal decisions in Fedora and help others get done the things that help our community.

  • Past work summary:

Package maintainer since the extras days: https://admin.fedoraproject.org/pkgdb/users/packages/kevin

I co-maintain the Xfce desktop packages.

Work with release engineering

I have served on FESCo for a long time.

Employed as Fedora Infrastructure lead to keep all our various infrastructure going.

Lots of other things...

  • Future plans:

Finish process changes to get Features moved to Changes and help streamline tracking.

Clean up and modernize some of our policies, especially non responsive maintainers policy.

Bill Nottingham (notting)

Introduction

  • 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, stability, 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. Work with those that show up to make changes, as, realistically, FESCo does not have a significant amount of resources to direct.

Peter Jones (pjones)

Introduction

  • 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 ensure that our processes for developers are as simple as possible, and to avoid processes that result in unnecessary work, or in duplication of effort, as we form new rules for change management in Fedora. 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 since 1998 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 of Fedora's packages for booty, cdparanoia, dumpet, gnu-efi, grub, grub2, grubby, 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 also represent Red Hat and Fedora on the UEFI Specification Working Group. 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 throughout Fedora. 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, especially as we revamp the Feature process.

Tomáš Mráz (t8m)

Introduction

  • Mission Statement:

Keeping Fedora as an usable and good quality operating system for running server and desktop applications.

  • Past work summary:

I've been Red Hat employee and Fedora contributor for more than eight years working on packages related to security (PAM, OpenSSL, libgcrypt, GNUTLS, ...) in both Fedora and Red Hat Enterprise Linux. I am one of the upstream maintainers of PAM. I was FESCo member for the past two years.

  • Future plans:

Apart from trying to adhere in my FESCo work to the mission statement above I'd like to help with implementation of the new change process and the Fedora revamp proposal. I'd also like to bring at least slightly more democracy into the FPC membership process.

Matthew Miller (mattdm)

Introduction

  • Mission Statement:
    • To see the Fedora distribution become more widely used as a platform, with modular layers of enabling technology all within the wider circle of the Fedora community.
  • Past work summary:
    • I've worked with Fedora since the beginning, as a community member and in my various roles as sysadmin and systems architect at Boston University and Harvard. (At BU, I helped host the very first FUDCons.) I've maintained a number of small packages for a long time. I was hired by Red Hat last year to work on Fedora Cloud, and have been working with others in the Cloud SIG to add polish to our Cloud images. I'm also on the Minimal Core SIG, which I care about both for the cloud images and because changes there ripple out and affect everyone. I'm often active on the mailing lists, and while I sometimes have strong opinions, I know I'm not always right and therefore try very hard to listen to all the different viewpoints.
  • Future plans:
    • I have a somewhat active vision for a Fedora project, centered around a base platform and with greater latitude for SIGs to solve problems within their areas. I'd like to see a more carefully managed (but not stagnant!) core OS, while allowing other layers to be less perfect when perfection is getting in their way — yet still hold those layers to standards agreed on by the Fedora community. Without both of these things, we risk becoming irrelevant: either beautiful but rarely used, or completely marginalized as we're passed by. Fedora is the best enthusiast distribution, and it can also be the best platform for development, the best cloud environment, and the base for a polished end-user experience.

Josh Boyer (jwb)

Introduction

  • Mission Statement:
    • To ensure Fedora remains a high quality, leading edge distribution with a variety of uses.
  • Past work summary:
    • I have been a Fedora user since its inception, and a Fedora contributor since around Fedora Core 4. In the past I've held positions on the Fedora Board and Fedora rel-eng teams. I was also part of the PowerPC secondary architecture effort. I've been on FESCo off and on since 2006. I am currently one of the three Fedora kernel maintainers, and I am a FESCo member running for re-election.
  • Future plans:
    • Continue to let developers and contributors accomplish what they need with a minimum amount of process and overhead. Help with the new change process as it evolves. Continue to look at the distro as a whole with an eye on improving the usability and function for a variety of targets.

Kalev Lember (kalev)

Introduction

  • Mission Statement:
    • Make sure Fedora stays relevant for both end users and developers.
  • Past work summary:
    • Fedora contributor for over 4 years, provenpackager and packager sponsor.
    • Co-handling the GNOME mass builds in Fedora.
    • Contributor to upstream GNOME.
    • Involved with the Fedora MinGW SIG since its beginning.
  • Future plans:
    • Try to make Rawhide a more usable platform for day-to-day use.
    • Fine tune the Branched release schedule and release engineering workflow to minimize rawhide bitrot. Right now Branched gets a lot of undivided attention for nearly 4 months before the release, and developers are off rawhide during that time.
    • Get Fedora back on track with its 6-month schedule, synced with upstreams that release every 6 months.