From Fedora Project Wiki
m (JohnPoelstra moved to User:Poelstra) |
|||
| (18 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
Hi, I'm John! | Hi, I'm John! | ||
A majority of my time as a Red Hat employee is dedicated to Fedora as ''Program Manager.'' This means I help with general project management | A majority of my time as a Red Hat employee is dedicated to Fedora as ''Program Manager.'' This means I help with general project management and act as the ''Feature Wrangler'' for new features in each new release. You'll also see me doing project management things like proposing and updating the release schedules, chasing blocker bugs, and facilitating our release readiness meetings. | ||
I also work on the [[BugZappers| Bug Triage process]]. | |||
For Fedora 12 and 13 I served as a [[Board | Fedora Board]] member. | |||
While I try to be as transparent as possible in my Fedora work, some of it is less visible when I am working with groups internal to Red Hat to make sure Fedora and Red Hat are aligned and working well together. | While I try to be as transparent as possible in my Fedora work, some of it is less visible when I am working with groups internal to Red Hat to make sure Fedora and Red Hat are aligned and working well together. | ||
== Project Goals == | == My Project Goals == | ||
* Releases that ship on time | |||
* A clear list of Features and their status for upcoming Fedora releases | * A clear list of Features and their status for upcoming Fedora releases | ||
* Predictable schedules that people can trust | * Predictable schedules that people can trust | ||
* Detailed schedules that remind everyone what it takes to complete a release and when those tasks need to be completed to finish on time | * Detailed schedules that remind everyone what it takes to complete a release and when those tasks need to be completed to finish on time | ||
* A smooth running | * A smooth running new Feature process | ||
* A well maintained bug tracking system | * A well maintained bug tracking system | ||
== | == How to Reach Me == | ||
* '''IRC''': irc.freenode.net with the nick '''poelcat''' | |||
** Channels: #fedora-meeting, #fedora-devel | |||
* '''email''': poelstra at fedoraproject org | |||
== What I'm Thinking About == | |||
* '''blog''': http://johnpoelstra.com | |||
* '''twitter''': http://twitter.com/johnpoelstra | |||
== | == More On My Background == | ||
* | * [http://www.linkedin.com/in/johnpoelstra John's LinkedIn Profile] | ||
Revision as of 21:50, 6 February 2011
John Poelstra, RHCE
$ whoami
Hi, I'm John!
A majority of my time as a Red Hat employee is dedicated to Fedora as Program Manager. This means I help with general project management and act as the Feature Wrangler for new features in each new release. You'll also see me doing project management things like proposing and updating the release schedules, chasing blocker bugs, and facilitating our release readiness meetings.
I also work on the Bug Triage process.
For Fedora 12 and 13 I served as a Fedora Board member.
While I try to be as transparent as possible in my Fedora work, some of it is less visible when I am working with groups internal to Red Hat to make sure Fedora and Red Hat are aligned and working well together.
My Project Goals
- Releases that ship on time
- A clear list of Features and their status for upcoming Fedora releases
- Predictable schedules that people can trust
- Detailed schedules that remind everyone what it takes to complete a release and when those tasks need to be completed to finish on time
- A smooth running new Feature process
- A well maintained bug tracking system
How to Reach Me
- IRC: irc.freenode.net with the nick poelcat
- Channels: #fedora-meeting, #fedora-devel
- email: poelstra at fedoraproject org
What I'm Thinking About
- blog: http://johnpoelstra.com
- twitter: http://twitter.com/johnpoelstra