<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>Folks,</div>
<div><br>
</div>
<div>Last year I found myself in the same position when I missed a deadline because my wrong planning and time zones nightmare!</div>
<div>However, the rules were very clear and I assumed my mistake. So, we should assume that we do not have candidates and follow the already described process. However, this should be very easy to figure out for the TC, it is just a matter to find our who is
interested in the PTL role and consulting with the core team of that specific project.</div>
<div><br>
</div>
<div>Just my two cents… </div>
<div><br>
</div>
<div>Edgar</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Kyle Mestery<br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)"<br>
<span style="font-weight:bold">Date: </span>Thursday, September 17, 2015 at 8:48 AM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)"<br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [all][elections] PTL nomination period is now over<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">On Thu, Sep 17, 2015 at 10:26 AM, Monty Taylor <span dir="ltr"><<a href="mailto:mordred@inaugust.com" target="_blank">mordred@inaugust.com</a>></span> wrote:<br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="">On 09/17/2015 04:50 PM, Anita Kuno wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 09/17/2015 08:22 AM, Matt Riedemann wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
On 9/17/2015 8:25 AM, Tristan Cacqueray wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
PTL Nomination is now over. The official candidate list is available on<br>
the wiki[0].<br>
<br>
There are 5 projects without candidates, so according to this<br>
resolution[1], the TC we'll have to appoint a new PTL for Barbican,<br>
MagnetoDB, Magnum, Murano and Security<br>
</blockquote>
<br>
This is devil's advocate, but why does a project technically need a PTL?<br>
Just so that there can be a contact point for cross-project things,<br>
i.e. a lightning rod? There are projects that do a lot of group<br>
leadership/delegation/etc, so it doesn't seem that a PTL is technically<br>
required in all cases.<br>
</blockquote>
<br>
I think that is a great question for the TC to consider when they<br>
evaluate options for action with these projects.<br>
<br>
The election officials are fulfilling their obligation according to the<br>
resolution:<br>
<a href="http://git.openstack.org/cgit/openstack/governance/tree/resolutions/20141128-elections-process-for-leaderless-programs.rst" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/governance/tree/resolutions/20141128-elections-process-for-leaderless-programs.rst</a><br>
<br>
If you read the verb there the verb is "can" not "must", I choose the<br>
verb "can" on purpose for the resolution when I wrote it. The TC has the<br>
option to select an appointee. The TC can do other things as well,<br>
should the TC choose.<br>
</blockquote>
<br>
</span>I agree- and this is a great example of places where human judgement is better than rules.<br>
<br>
For instance - one of the projects had a nominee but it missed the deadline, so that's probably an easy on.<br>
<br>
For one of the projects it had been looking dead for a while, so this is the final nail in the coffin from my POV<br>
<br>
For the other three - I know they're still active projects with people interested in them, so sorting them out will be fun!
<div class="HOEnZb">
<div class="h5"><br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>This is the right approach. Human judgement #ftw! :)<br>
<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb">
<div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
There are 7 projects that will have an election: Cinder, Glance, Ironic,<br>
Keystone, Mistral, Neutron and Oslo. The details for those will be<br>
posted tomorrow after Tony and I setup the CIVS system.<br>
<br>
Thank you,<br>
Tristan<br>
<br>
<br>
[0]:<br>
<a href="https://wiki.openstack.org/wiki/PTL_Elections_September_2015#Confirmed_Candidates" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/PTL_Elections_September_2015#Confirmed_Candidates</a><br>
<br>
[1]:<br>
<a href="http://governance.openstack.org/resolutions/20141128-elections-process-for-leaderless-programs.html" rel="noreferrer" target="_blank">http://governance.openstack.org/resolutions/20141128-elections-process-for-leaderless-programs.html</a><br>
<br>
<br>
<br>
<br>
<br>
__________________________________________________________________________<br>
<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
<br>
</blockquote>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</span>
</body>
</html>