Jump to: navigation, search

Difference between revisions of "Documentation/ProjectDocLeads"

(Potential Candidates)
Line 7: Line 7:
 
Object Storage (Swift): Chuck Thier
 
Object Storage (Swift): Chuck Thier
  
Image Service (Glance): Iccha Sethi **
+
Image Service (Glance): Iccha Sethi *
  
 
Identity (Keystone): Adam Young?
 
Identity (Keystone): Adam Young?
Line 13: Line 13:
 
Dashboard (Horizon): Julie Pichon?
 
Dashboard (Horizon): Julie Pichon?
  
Networking (Neutron): Edgar Magana **
+
Networking (Neutron): Edgar Magana *
  
Block Storage (Cinder): Mike Perez **
+
Block Storage (Cinder): Mike Perez *
  
 
Metering/Monitoring (Ceilometer): Doug Hellman?
 
Metering/Monitoring (Ceilometer): Doug Hellman?

Revision as of 18:46, 13 August 2013

A few of us were batting around ideas of how to improve and speed the release cycle during the last summit. The simplest idea that came out of that discussion was the concept of a Project Documentation Lead or PDL. The idea is the PDL would be part of the regular project leadership and would likely be an active contributing technical member of the project. There would need to be at least some dotted line responsibility to your role leading the documentation. The PDL would be responsible for tracking and updating the docs for all things related to their project throughout the release cycle.

Potential Candidates

Compute (Nova): Jog0 or Michael Still?

Object Storage (Swift): Chuck Thier

Image Service (Glance): Iccha Sethi *

Identity (Keystone): Adam Young?

Dashboard (Horizon): Julie Pichon?

Networking (Neutron): Edgar Magana *

Block Storage (Cinder): Mike Perez *

Metering/Monitoring (Ceilometer): Doug Hellman?

Orchestration (Heat): Randall Burt?

Database Service (Trove):

Bare metal (Ironic):

Common Libraries (Oslo):

* These people have identified themselves as point person for docs on the project.