[TC] 'V' Technical Elections
gmann at ghanshyammann.com
Fri Dec 6 15:08:19 UTC 2019
---- On Fri, 06 Dec 2019 01:15:45 -0600 Kendall Nelson <kennelson11 at gmail.com> wrote ----
> Hello Everyone!
> To summarize the TC office hours discussions today:
> - The majority of folks are in favor of a combined election- With the combined election dates above, those TC members seat that will be up for reelection will hit their term limite before we conclude the election so there will be a period of time where the TC will only be 6 members until the election concludes. - In an effor to avoid this expiration and gap in having a full TC in the future, we want to amend the charter to say something about term limits being '14 months or when the second election since being elected concludes' or something like that-- theres another thread for that discussion '[TC] Election Terms'- We will need to move the extra-atc deadline forward so that it is during the week of nominations so that they can be included in the electorates
> I think that covers all of it. If I missed anything, please feel free to expand :)
I think that is all. During the half-tc period, we will not be able to merge any charter change which should be ok.
> If we, the election officials don't hear anything by the end of next week, we will move froward updating the election site and the release schedule.
>  http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2019-12-05.log.html#t2019-12-05T15:46:11
> On Wed, Dec 4, 2019 at 3:01 PM Kendall Nelson <kennelson11 at gmail.com> wrote:
> /me takes TC hat off and puts election official hat on
> Having run our handy dandy tool to project dates for the elections, we have some decisions to make again.
> At this point we have threeish options:
> 1. Run the elections with a week in between with the TC election happening BEFORE the PTL election like the script generated. The TC election would run March 10 to March 31 and the PTL Election would run April 7 to April 21. The primary concern here is that it might lead to some election burnout.
> 2. Run the elections back to back with the PTL election first (closer to the historic norm). This would be tweaking the generated dates by pulling the PTL election three weeks up and pushing back the TC dates by two weeks. The PTL election would run March 3 to March 17 and the PTL Election would run March 17 to April 7. Both elections would be concluded by milestone 3. Similar concerns with this option to the first with election burnout.
> 3. Run the elections in parallel as a combined election, similar to how we did for the Train elections. This is much easier for election officials because we only need to generate one electorate. The two elections would start March 10 and be done by March 31 following the TC election model with a nominations period, a campaigning period (optional for PTL elections), and then a polling period (assuming we need a runoff).
> Other info to keep in mind when formulating your opinions:
> - Extra ATC deadline currently is March 23-27 which will likely need to get bumped earlier for any of these options
> - RC1 is the week of April 20-24
> - Milestone 3 is April 9
> - Release schedule for reference
> - For TC member terms, those closing in on their ~1 year terms would be closer to 13 months since the train elections concluded March 5th of last year
> -Kendall (diablo_rojo) & the Election Officials
More information about the openstack-discuss