Development/SteeringCommittee/Nominations

From FedoraProject

< Development | SteeringCommittee(Difference between revisions)
Jump to: navigation, search
(Person Name (IRC nickname))
Line 8: Line 8:
 
* '''Past work summary:'''
 
* '''Past work summary:'''
 
* '''Future plans:'''
 
* '''Future plans:'''
 +
 +
== [[User:jforbes|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.

Revision as of 14:03, 28 October 2011

For the last election, see Development/SteeringCommittee/NominationsJune2011

In the November 2011 election, there are 4 seats open. Seats are currently held by: Adam Jackson (ajax), Christoph Wickert (cwickert), Matthew Garrett (mjg59), and Marcela Mašláňová (mmaslano).

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.