From bcadd43617716640574b3fb3756227c1a4331474 Mon Sep 17 00:00:00 2001 From: Thierry Carrez Date: Thu, 13 Oct 2016 11:58:31 +0200 Subject: [PATCH] Adjust TC and PTL election timeframes With the Design Summit functions being split between the OpenStack Summit and the Project Teams Gathering, the current wording in the TC charter around election (which uses "Design Summit" and "Summit" interchangeably) is no longer valid. This change clarifies the situation by: * keeping PTL elections near to development cycle boundaries (but defining the timeframe relative to release rather than relative to an event) * keeping TC elections on a 6-month spring/fall cadence, organizing them relative to the OpenStack Summit dates The change is compatible with the language around TC elections present in the OpenStack Foundation bylaws (esp. Appendix 4), which mentions 6-month and one-year periods but does not attach TC elections to events or cycles. This change therefore should not require any change on the bylaws side. While it tries to minimize impact, the net result of the change is that TC elections are now separate from PTL elections (rather than run just the week after). This change also adds some flexibility in vote organization, by: * using "on or before" language to allow election officials to work around holidays * removing language around nomination periods (potentially allowing for the addition of "campaign days" between nomination and vote) * lowering the minimum required amount of voting days to 4 business days (potentially allowing the vote to be organized within a week rather than forcing it to overlap with a weekend) Change-Id: I5900f9b4a10cbdb09609516d0b04f29b4fe7eb88 --- reference/charter.rst | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/reference/charter.rst b/reference/charter.rst index d05bc4f83..5b4968ddd 100644 --- a/reference/charter.rst +++ b/reference/charter.rst @@ -99,10 +99,10 @@ than two votes. Election for PTL seats ====================== -PTL seats are completely renewed every 6 months. A separate election is run for -each project team. These elections are collectively held 5 weeks prior to each -design summit, with nominations due 6 weeks prior to the summit and elections -held open for no less than five business days. +PTL seats are completely renewed every development cycle. A separate election +is run for each project team. These elections are collectively held no later +than 3 weeks prior to each cycle final release date (on or before 'R-3' week) +and should be held open for no less than four business days. Voters for PTL seats ("APC") ============================ @@ -125,9 +125,9 @@ Election for TC seats The 13 TC seats are partially renewed every 6 months using staggered elections: 6 seats are renewed every (Northern hemisphere) Fall, and 7 seats are renewed every Spring. Seats are valid for one-year terms. For this election we'll use a -multiple-winner election system (see below). The election is held 3 weeks prior -to each design summit, with nominations due 4 weeks prior to the summit and -elections held open for no less than five business days. +multiple-winner election system (see below). The election is held no later than +3 weeks prior to each OpenStack Summit (on or before 'S-3' week), with +elections held open for no less than four business days. If a seat on the TC is vacated before the end of the term for which the member was elected, the TC will select a replacement to serve out