<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Thu, Aug 22, 2013 at 8:38 AM, Don Schenck <span dir="ltr"><<a href="mailto:don.schenck@rackspace.com" target="_blank">don.schenck@rackspace.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">Help a newbie: "PTL"??<br></blockquote><div><br>
</div><div>"<span style="color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;font-size:14px;line-height:20px">Project Technical Leads (PTLs) lead individual projects. A PTL is ultimately responsible for the direction for each project, makes tough calls when needed, organizes the work and teams in the project and determines if other forms of project leadership are needed. The PTL for a project is elected by the body of contributors to that particular project."</span></div>
<div><span style="color:rgb(51,51,51);font-family:'Arial Unicode MS',Arial,sans-serif;font-size:14px;line-height:20px"> - </span><font color="#333333" face="Arial Unicode MS, Arial, sans-serif"><span style="font-size:14px;line-height:20px"><a href="https://wiki.openstack.org/wiki/Governance/Foundation/Structure">https://wiki.openstack.org/wiki/Governance/Foundation/Structure</a></span></font><br>
</div><div> </div><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=""><div class="h5"><br>
-----Original Message-----<br>
From: Tomas Sedovic [mailto:<a href="mailto:tsedovic@redhat.com">tsedovic@redhat.com</a>]<br>
Sent: Thursday, August 22, 2013 8:55 AM<br>
To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
Subject: [openstack-dev] Tuskar PTL candidacy<br>
<br>
I would like to nominate myself for the role of Tuskar PTL.<br>
<br>
While not senior by any stretch of imagination, I did QA automation for three years and development for another three (professionally; I've been coding on my own since I was 13) so I'm familiar with both sides of the table.<br>
<br>
I've helped with the development of the Heat project during its first six months and got one of the early releases out the door (pre-incubation iirc). I'm familiar with the OpenStack processes, I'd attended weekly Heat meetings and been helping my colleagues with the transition from a Ruby on Rails github workflow to the OpenStack way of development.<br>
<br>
I'll freely admit I'm not the most knowledgeable person around. But I'm not afraid to ask questions or admit being wrong and I tend to learn quickly.<br>
<br>
Apart from more features and stability, I'll push Tuskar towards clear documentation and friendliness to newcomers.<br>
<br>
--<br>
Tomas Sedovic<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><br></div>-Dolph
</div></div>