From Fedora Project Wiki

No edit summary
No edit summary
 
(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, act as the ''Feature Wranger'' for new features in each new release, and whatever else helps Fedora to be a better project.  Most recently this includes working with [[JonStanley|  Jon Stanley]]  to relaunch the [[BugZappers|  Bug Triage process]] .
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.


You'll also see me publishing minutes for all of the Fedora Board meetings as a secretary, publishing recaps for [[ReleaseEngineering| Release Engineering]] Meetings too, and doing install testing for new releases.
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.


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 For Fedora Were ==
 
* Releases that ship on time
== 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


== (occasional) Blog ==
== 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 [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'''
** Channels: #openshift
* '''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]
* email: poelstra/.\at/.\fedoraproject.org

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