<div dir="ltr">Midway is still on earth. :)</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 17, 2015 at 10:35 AM, Neil Jerram <span dir="ltr"><<a href="mailto:Neil.Jerram@metaswitch.com" target="_blank">Neil.Jerram@metaswitch.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">But on the Internet, no one knows that I'm really a crocodile, and<br>
writing from Midway...<br>
<br>
    Neil<br>
<span class=""><br>
<br>
On 17/09/15 18:29, Kevin Benton wrote:<br>
><br>
> Maybe it would be a good idea to switch to 23:59 AOE deadlines like<br>
> many paper submissions use for academic conferences. That way there is<br>
> never a need to convert TZs, you just get it in by the end of the day<br>
> in your own time zone.<br>
><br>
> On Sep 17, 2015 9:18 AM, "Edgar Magana" <<a href="mailto:edgar.magana@workday.com">edgar.magana@workday.com</a><br>
</span><span class="">> <mailto:<a href="mailto:edgar.magana@workday.com">edgar.magana@workday.com</a>>> wrote:<br>
><br>
>     Folks,<br>
><br>
>     Last year I found myself in the same position when I missed a<br>
>     deadline because my wrong planning and time zones nightmare!<br>
>     However, the rules were very clear and I assumed my mistake. So,<br>
>     we should assume that we do not have candidates and follow the<br>
>     already described process. However, this should be very easy to<br>
>     figure out for the TC, it is just a matter to find our who is<br>
>     interested in the PTL role and consulting with the core team of<br>
>     that specific project.<br>
><br>
>     Just my two cents…<br>
><br>
>     Edgar<br>
><br>
>     From: Kyle Mestery<br>
>     Reply-To: "OpenStack Development Mailing List (not for usage<br>
>     questions)"<br>
>     Date: Thursday, September 17, 2015 at 8:48 AM<br>
>     To: "OpenStack Development Mailing List (not for usage questions)"<br>
>     Subject: Re: [openstack-dev] [all][elections] PTL nomination<br>
>     period is now over<br>
><br>
>     On Thu, Sep 17, 2015 at 10:26 AM, Monty Taylor<br>
</span><div><div class="h5">>     <<a href="mailto:mordred@inaugust.com">mordred@inaugust.com</a> <mailto:<a href="mailto:mordred@inaugust.com">mordred@inaugust.com</a>>> wrote:<br>
><br>
>         On 09/17/2015 04:50 PM, Anita Kuno wrote:<br>
><br>
>             On 09/17/2015 08:22 AM, Matt Riedemann wrote:<br>
><br>
><br>
><br>
>                 On 9/17/2015 8:25 AM, Tristan Cacqueray wrote:<br>
><br>
>                     PTL Nomination is now over. The official candidate<br>
>                     list is available on<br>
>                     the wiki[0].<br>
><br>
>                     There are 5 projects without candidates, so<br>
>                     according to this<br>
>                     resolution[1], the TC we'll have to appoint a new<br>
>                     PTL for Barbican,<br>
>                     MagnetoDB, Magnum, Murano and Security<br>
><br>
><br>
>                 This is devil's advocate, but why does a project<br>
>                 technically need a PTL?<br>
>                   Just so that there can be a contact point for<br>
>                 cross-project things,<br>
>                 i.e. a lightning rod?  There are projects that do a<br>
>                 lot of group<br>
>                 leadership/delegation/etc, so it doesn't seem that a<br>
>                 PTL is technically<br>
>                 required in all cases.<br>
><br>
><br>
>             I think that is a great question for the TC to consider<br>
>             when they<br>
>             evaluate options for action with these projects.<br>
><br>
>             The election officials are fulfilling their obligation<br>
>             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<br>
>             choose the<br>
>             verb "can" on purpose for the resolution when I wrote it.<br>
>             The TC has the<br>
>             option to select an appointee. The TC can do other things<br>
>             as well,<br>
>             should the TC choose.<br>
><br>
><br>
>         I agree- and this is a great example of places where human<br>
>         judgement is better than rules.<br>
><br>
>         For instance - one of the projects had a nominee but it missed<br>
>         the deadline, so that's probably an easy on.<br>
><br>
>         For one of the projects it had been looking dead for a while,<br>
>         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<br>
>         with people interested in them, so sorting them out will be fun!<br>
><br>
><br>
>     This is the right approach. Human judgement #ftw! :)<br>
><br>
><br>
><br>
><br>
><br>
><br>
>                     There are 7 projects that will have an election:<br>
>                     Cinder, Glance, Ironic,<br>
>                     Keystone, Mistral, Neutron and Oslo. The details<br>
>                     for those will be<br>
>                     posted tomorrow after Tony and I setup the CIVS<br>
>                     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<br>
>                     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>
</div></div>>                     <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
<span class="">>                     <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>
><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>
</span>>             <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
<span class="">>             <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>
><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>
</span>>         <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
<span class="">>         <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>
><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>
</span>>     <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
<div class="HOEnZb"><div class="h5">>     <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>
<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><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div>Kevin Benton</div></div>
</div>