<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-1">
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-1">
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-1">
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-1">
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-1">
<p><font style="font-size: 11pt" size="2">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
A:link { so-language: zxx }
-->
</style>
<p><font style="font-size: 11pt" size="2">I would also like to
nominate
myself for the role of Tuskar PTL.<br>
<br>
</font></p>
I am a senior engineer at Red
Hat where I have been part of the core Tuskar engineering team
since
its inception, participating in the various discussions and
technical
decisions for the initial Tuskar proof of concept. I helped
define
our integration points with existing OpenStack projects which
required understanding of Triple O, Heat and Nova Bare Metal.<br>
</font></p>
<p><font style="font-size: 11pt" size="2">Over the past few years
I
have been involved with building cross cloud management tools
(Aeolus, Deltacloud). I chaired the Aeolus technical cabal and
led
efforts on the Template and Image Management tool 'TIM'.
During this
time I also </font><span style="font-variant: normal"><font
color="#000000"><font style="font-size: 11pt" size="2"><span
style="font-style: normal"><span style="font-weight:
normal">designed
and implemented a number REST APIs and recently
contributed the
initial Ironic REST API design spec. </span></span></font></font></span><font
style="font-size: 11pt" size="2">I
have experience integrating with a number of other OpenStack
projects: Glance, Keystone and Horizon from building out a
proof of
concept for an OpenStack image building service:
<a href="http://www.youtube.com/watch?v=MdBM4HA3QUk">http://www.youtube.com/watch?v=MdBM4HA3QUk</a>.
I have a good overall understanding of what each project
offers and
how we can utilize them to achieve our goal in Tuskar.<br>
<br>
</font></p>
<p><font style="font-size: 11pt" size="2">I am convinced that the
right
approach with Tuskar is to act as a consumer of existing
OpenStack
projects, utilizing the services these projects offer as much
as
possible. This should allow us to keep a tight focus on our
main goal of 'Deploying and managing OpenStack at large
scales'.
To achieve this we'll need to be heavily involved in the
OpenStack
community at large <font size="2">and actively</font>
contributing
features to upstream projects when necessary.<br>
<br>
</font></p>
<font style="font-size: 11pt" size="2">I am very excited about the
Tuskar project and becoming more involved with the OpenStack
community at large, watching Tuskar grow over the 6 months
should
be very interesting.</font><br>
<p><font style="font-size: 11pt" size="2">Regards<br>
Martyn</font></p>
<title></title>
<meta name="GENERATOR" content="LibreOffice 3.6 (Linux)">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
A:link { so-language: zxx }
-->
</style>
<p><br>
On 22/08/13 14:54, Dolph Mathews wrote:<br>
</p>
</div>
<blockquote
cite="mid:CAC=h7gVR8mSXCx+ski0SDJFopyUhMMWosm5_2X4sC=32LTWk_w@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
<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 moz-do-not-send="true"
href="mailto:don.schenck@rackspace.com" target="_blank">don.schenck@rackspace.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote">Help a newbie: "PTL"??<br>
</blockquote>
<div><br>
</div>
<div>"<span>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> - </span><span><a moz-do-not-send="true"
href="https://wiki.openstack.org/wiki/Governance/Foundation/Structure">https://wiki.openstack.org/wiki/Governance/Foundation/Structure</a></span><br>
</div>
<div> </div>
<blockquote class="gmail_quote">
<div class="">
<div class="h5"><br>
-----Original Message-----<br>
From: Tomas Sedovic [mailto:<a moz-do-not-send="true"
href="mailto:tsedovic@redhat.com">tsedovic@redhat.com</a>]<br>
Sent: Thursday, August 22, 2013 8:55 AM<br>
To: <a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a moz-do-not-send="true"
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>
<div><br>
</div>
-- <br>
<div><br>
</div>
-Dolph
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>