From dd0168720be6eb201b22d231946fbabbdc97fb3d Mon Sep 17 00:00:00 2001 From: Ghanshyam Mann Date: Fri, 10 Feb 2023 17:20:29 -0600 Subject: [PATCH] Make DPL/PTL model change deadline as election nomination start Once the election are started it is difficult to change the list of projects need election so any DPL or PTL model change request should be merged before the election nomination start. Change-Id: Ia1544d4541926c8f689e0e6f361b7057ed28b64d --- resolutions/20200803-distributed-project-leadership.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/resolutions/20200803-distributed-project-leadership.rst b/resolutions/20200803-distributed-project-leadership.rst index 624a08153..92242e13c 100644 --- a/resolutions/20200803-distributed-project-leadership.rst +++ b/resolutions/20200803-distributed-project-leadership.rst @@ -185,7 +185,8 @@ It must also get a +1 from the future PTL, listed in the same change. A project team may change their opt-in status only once a release cycle, to ensure that the elections officials have clarity on which project teams need PTL -elections. All requests should be received by week R-5 of the release calendar. +elections. All requests should be merged before the election nominations start +otherwise request will be postponed to the next cycle. The distributed leadership model is only requested explicitly. If a project team has no candidate for PTL, the TC will still evaluate the future of the