<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Aug 22, 2014 at 9:13 AM, Daniel P. Berrange <span dir="ltr"><<a href="mailto:berrange@redhat.com" target="_blank">berrange@redhat.com</a>></span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="">On Fri, Aug 22, 2014 at 02:33:27PM +0200, Thierry Carrez wrote:<br>


> Hi everyone,<br>
><br>
> We all know being a project PTL is an extremely busy job. That's because<br>
> in our structure the PTL is responsible for almost everything in a project:<br>
><br>
> - Release management contact<br>
> - Work prioritization<br>
> - Keeping bugs under control<br>
> - Communicate about work being planned or done<br>
> - Make sure the gate is not broken<br>
> - Team logistics (run meetings, organize sprints)<br>
> - ...<br>
<br>
</div><br>
Is there any formal writeup of the PTL role's responsibilities ?<br><br></blockquote><div><br></div><div>Formal? Not really. But here's my informal perspective:</div><div><br></div><div>  <a href="http://dolphm.com/responsibilities-of-an-openstack-program-technical-lead-ptl">http://dolphm.com/responsibilities-of-an-openstack-program-technical-lead-ptl</a></div>

<div><br></div></div></div></div>