<div dir="ltr">Hello!<div><br></div><div><div class="gmail_quote"><div dir="ltr">On Tue, Aug 7, 2018 at 9:39 PM Tony Breeds <<a href="mailto:tony@bakeyournoodle.com">tony@bakeyournoodle.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello all,<br>
With the PTL elections behind us it's time to start looking at the<br>
TC election. Our charter[1] says:<br>
<br>
The election is held no later than 6 weeks prior to each OpenStack<br>
Summit (on or before ‘S-6’ week), with elections held open for no less<br>
than four business days.<br>
<br>
Assuming we have the same structure that gives us a timeline of:<br>
<br>
Summit is at: 2018-11-13<br>
Latest possible completion is at: 2018-10-02<br>
Moving back to Tuesday: 2018-10-02<br>
TC Election from 2018-09-25T23:45 to 2018-10-02T23:45<br>
TC Campaigning from 2018-09-18T23:45 to 2018-09-25T23:45<br>
TC Nominations from 2018-09-11T23:45 to 2018-09-18T23:45<br>
<br>
This puts the bulk of the nomination period during the PTG, which is<br>
sub-optimal as the nominations cause a distraction from the PTG but more<br>
so because the campaigning will coincide with travel home, and some<br>
community members take vacation along with the PTG.<br>
<br>
So I'd like to bring up the idea of moving the election forward a<br>
little so that it's actually the campaigning period that overlaps with<br>
the PTG:<br>
<br>
TC Election from 2018-09-18T23:45 to 2018-09-27T23:45<br>
TC Campaigning from 2018-09-06T23:45 to 2018-09-18T23:45<br>
TC Nominations from 2018-08-30T23:45 to 2018-09-06T23:45<br></blockquote><div> </div><div>+2!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This gives us longer campaigning and election periods.<br>
<br>
There are some advantages to doing this:<br>
<br>
* A panel style Q&A could be held formally or informally ;P<br>
* There's improved scope for for incoming, outgoing and staying put TC<br>
members to interact in a high bandwidth way.<br>
* In personi/private discussions with TC candidates/members.<br>
<br>
However it isn't without downsides:<br>
<br>
* Election fatigue, We've just had the PTL elections and the UC<br>
elections are currently running. Less break before the TC elections<br>
may not be a good thing.<br></blockquote><div><br></div><div>Simultaneously, would be nice to get it done with.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
* TC candidates that can't travel to the PTG could be disadvantaged<br></blockquote><div><br></div><div>We also can and should post things on the ML for longer discussion as the 'debate' likely wouldn't be much longer than over lunch one day. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
* The campaigning would all happen at the PTG and not on the mailing<br>
list disadvantaging community members not at the PTG.<br>
<br>
So thoughts?<br></blockquote><div><br></div><div>I think this is a good plan :) Ready to +2 the config change as soon as I see it. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Yours Tony.<br>
<br>
[1] <a href="https://governance.openstack.org/tc/reference/charter.html" rel="noreferrer" target="_blank">https://governance.openstack.org/tc/reference/charter.html</a><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></blockquote><div><br></div><div>-Kendall (diablo_rojo) </div></div></div></div>