From Fedora Project Wiki

No edit summary
 
(5 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 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 and facilitating our release readiness meetings.
I was Fedora's first  ''Program Manager.''  This meant I helped with general project management and acted as the ''Feature Wrangler'' for new features in each new release and with the help of some others drafted and implemented the first official Fedora Feature process. I also did 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]].
I worked on the [[BugZappers| Bug Triage process]] and served as a [[Board | Fedora Board]] member during the or Fedora 12 and 13 release cycles.


For Fedora 12 and 13 I served as a [[Board | Fedora Board]] member.
== My Project Goals For Fedora Were ==
 
* Releases that ship on time
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 ==
* 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


== More About My Background ==
== Now() ==
* [http://www.linkedin.com/in/johnpoelstra John's Linked In Profile]


== How to Reach or Follow Me ==
I'm not currently active in the Fedora community, though I do run Fedora on one of my notebooks that I use in my role as Product Marketing Manager at Red Hat where I've worked since 2004.  I often draw on the experiences and lessons I learned in Fedora while helping to guide the direction of [https://openshift.redhat.com OpenShift PaaS] and the community we are working to develop there.
 
== How to Reach Me ==
* '''IRC''': irc.freenode.net with the nick '''poelcat'''
* '''IRC''': irc.freenode.net with the nick '''poelcat'''
** Channels: #fedora-meeting, #fedora-devel
** Channels: #openshift
* '''email''': poelstra at fedoraproject org
* '''email''': poelstra at fedoraproject org
* '''blog''': http://poelcat.wordpress.com  
 
== What I'm Thinking About ==
* '''blog''': http://johnpoelstra.com  
* '''twitter''': http://twitter.com/johnpoelstra
* '''twitter''': http://twitter.com/johnpoelstra
== More On My Background ==
* [http://www.linkedin.com/in/johnpoelstra John's LinkedIn Profile]

Latest revision as of 03:04, 6 January 2013

John Poelstra, RHCE

$ whoami

Hi, I'm John!

I was Fedora's first Program Manager. This meant I helped with general project management and acted as the Feature Wrangler for new features in each new release and with the help of some others drafted and implemented the first official Fedora Feature process. I also did project management things like proposing and updating the release schedules, chasing blocker bugs, and facilitating our release readiness meetings.

I worked on the Bug Triage process and served as a Fedora Board member during the or Fedora 12 and 13 release cycles.

My Project Goals For Fedora Were

  • 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

Now()

I'm not currently active in the Fedora community, though I do run Fedora on one of my notebooks that I use in my role as Product Marketing Manager at Red Hat where I've worked since 2004. I often draw on the experiences and lessons I learned in Fedora while helping to guide the direction of OpenShift PaaS and the community we are working to develop there.

How to Reach Me

  • IRC: irc.freenode.net with the nick poelcat
    • Channels: #openshift
  • email: poelstra at fedoraproject org

What I'm Thinking About

More On My Background