From 03958456aceeded0dfc9eaa4a0644fcdd7726e0e Mon Sep 17 00:00:00 2001 From: Emmet Hikory Date: Fri, 11 Aug 2017 00:16:37 +0900 Subject: [PATCH] Amend leaderless program resolution timeframe The current language puts undue pressure on election officials to immediately notify the TC in the event of a leaderless project, while also not providing a maximum timeframe for notification, which may leave a project leaderless for some time in exceptional circumstances. The replacement language places a clear bound on the notification period, allowing election officials to take care with their reporting, and the technical committee to have information in a timeframe that allows a new PTL to be selected to start with their peers. Change-Id: Id82afaf24b6fd8f8db90df635debc38a04627791 --- .../20141128-elections-process-for-leaderless-programs.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/resolutions/20141128-elections-process-for-leaderless-programs.rst b/resolutions/20141128-elections-process-for-leaderless-programs.rst index b8fc91b84..419941c01 100644 --- a/resolutions/20141128-elections-process-for-leaderless-programs.rst +++ b/resolutions/20141128-elections-process-for-leaderless-programs.rst @@ -8,8 +8,8 @@ eligible candidate identify themselves, the following process will be used to determine leadership for any program in this situation. #. Programs without a minimum of one eligible candidate are identified to the - Technical Committee by the Election Officials, as soon as possible after the - nomination period has expired. + Technical Committee by the Election Officials, before the conclusion of + the election. #. The Technical Committee can appoint a leader to any programs in this situation, by mutual agreement of the Technical Committee and the proposed