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, act as the ''Feature Wranger'' for new features in each new release, and whatever else helps Fedora to be a better project. I am also currently helping to lead the [[BugZappers| Bug Triage process]] .

+

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.

−

You'll also see me publishing minutes for all of the Fedora Board meetings as the secretary and doing project management things like updating the schedule and proposing new schedules for the next release.

+

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 Fedora project

+

* A smooth running new Feature process

* A well maintained bug tracking system

* A well maintained bug tracking system

−

== (occasional) Blog ==

+

== How to Reach Me ==

+

* '''IRC''': irc.freenode.net with the nick '''poelcat'''

+

** Channels: #fedora-meeting, #fedora-devel

+

* '''email''': poelstra at fedoraproject org

−

[http://poelcat.wordpress.com poelcat.wordpress.com]

+

== What I'm Thinking About ==

+

* '''blog''': http://johnpoelstra.com

+

* '''twitter''': http://twitter.com/johnpoelstra

−

== How to reach me ==

+

== More On My Background ==

−

* '''IRC''': irc.freenode.net with the nick '''poelcat'''

+

* [http://www.linkedin.com/in/johnpoelstra John's LinkedIn Profile]

−

** Channels: #fedora-bugzappers, #fedora-meeting, #fedora-qa

+

−

* '''email''': poelstra/.\at/.\fedoraproject.org

+

−

* '''twitter''': poelcat

+

Revision as of 21:50, 6 February 2011

Contents

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.

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