Open Stack

Kendall Nelson wrote:
> [...]
> So, basically if we follow the usual formulas for when to hold the TC 
> and PTL elections, they overlap a bit but not nicely. You can see what 
> the dates would be if we exactly followed the usual timeline in this 
> etherpad[1].
> 
> The proposal from the election officials is that we move the PTL 
> nominations 1 week early and that gives them 1-week idle time in which 
> we *could* do campaigning for PTLs the same way we do campaigning for TC 
> seats. We definitely don't have to do campaigning, it could just be a 
> week of idle time while TC campaigning happens.
> 
> Setting Combined Election
> Summit is at: 2019-11-04
> Release is at: 2019-10-14
> Latest possible completion is at: 2019-09-23
> Moving back to Tuesday: 2019-09-17
> TC Election from 2019-09-10T23:45 to 2019-09-17T23:45
> PTL Election from 2019-09-10T23:45 to 2019-09-17T23:45
> TC Campaigning from 2019-09-03T23:45 to 2019-09-10T23:45
> TC Nominations from 2019-08-27T23:45 to 2019-09-03T23:45
> PTL Nominations from 2019-08-27T23:45 to 2019-09-03T23:45
> Set email_deadline to 2019-09-03T00:00
> Setting TC timeframe end to email_deadline
> Beginning of Stein Cycle @ 2018-08-10 00:00:00+00:00
> End of Train cycle @ 2019-09-03 00:00:00+00:00
> Election timeframe: 389 days, 0:00:00s
> 
> This format makes it easier for election officials since we would only 
> need to generate the electorate once for both elections. We can create 
> whatever polls we need to for PTL elections at the same time we make the 
> TC election poll. All in all less confusing for the electorate as well 
> (hopefully).

We historically placed TC elections after PTL elections because some 
people found it useful to know if they were elected PTL before running 
(or not running) for a TC seat.

Is that still a concern? If not, I think it's just easier to do both at 
the same time (nominations, campaigning, election).

-- 
Thierry Carrez (ttx)