Jump to: navigation, search

Difference between revisions of "Heat/PTLGuide"

(Heat Core Team)
(PTL Group)
Line 8: Line 8:
 
=== PTL Group ===
 
=== PTL Group ===
  
The PTL should be a member of the [https://review.openstack.org/#/admin/groups/152,members `heat-ptl` group] in Gerrit. This allows you to approve backproted patches on stable branches. Get the previous PTL to add you. Most teams remove previous PTLs from this group so that it generally has only member. To date, Heat has not bothered to follow this practice (this means no single point of failure, at a potential cost of a higher chance of someone accidentally approving a backported patch).
+
The PTL should be a member of the [https://review.openstack.org/#/admin/groups/152,members `heat-ptl` group] in Gerrit. This is somewhat misnamed, and allows you to approve backported patches on stable branches. Get the previous PTL to add you. Having past PTLs in this group is actually encouraged (this means no single point of failure, at a potential cost of a higher chance of someone accidentally approving a backported patch). To date, Heat has not bothered to remove any of the previous PTLs.
  
 
=== Heat Core Team ===
 
=== Heat Core Team ===

Revision as of 20:09, 27 May 2014

This page is intended to collect information on the duties of the Program Technical Lead for Orchestration.

OpenStack Responsibilities

The PTL is accountable to the OpenStack community (and, in particular, the Technical Committee) for ensuring that the program fulfills the requirements of an OpenStack program. Read the PTLguide for details.

Gerrit Groups

PTL Group

The PTL should be a member of the `heat-ptl` group in Gerrit. This is somewhat misnamed, and allows you to approve backported patches on stable branches. Get the previous PTL to add you. Having past PTLs in this group is actually encouraged (this means no single point of failure, at a potential cost of a higher chance of someone accidentally approving a backported patch). To date, Heat has not bothered to remove any of the previous PTLs.

Heat Core Team

The PTL generally acts behind the scenes to collect feedback on various potential members for the Heat/CoreTeam, and can co-ordinate with candidates to ensure that they are interested and have the time available, as well as give them feedback in private on what they need to work on. If a candidate is approved by the core team, add them to the `heat-core` group in Gerrit.

To ensure the correct designation of core team members in the review statistics, you should also update the reviewstats tool with the appropriate Gerrit username. The easiest way to find the right username is by looking at the stats.

Design Summit Organisation

The PTL is the only person with access to conduct the scheduling of the Design Summit sessions for Heat. It is recommended to use an Etherpad to collect feedback, and to start early because the timeframe is very tight between when submissions close and when the sessions need to be scheduled.