From 5bff5d1bac1ac3c86be4c3fd06cb5a9307cc8668 Mon Sep 17 00:00:00 2001 From: Ghanshyam Mann <gmann@ghanshyammann.com> Date: Wed, 7 Aug 2024 15:06:48 -0700 Subject: [PATCH] Update DPL model reset steps To avoid the mulitple changes in the DPL reset state, this adds the option of 'opt-in' via -1 (from all the liaisons) the DPL reset state. Change-Id: Ife0006cfa29340411ecf23ea41862e1b1b434236 --- reference/distributed-project-leadership.rst | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/reference/distributed-project-leadership.rst b/reference/distributed-project-leadership.rst index 021b3d900..dbce463d1 100644 --- a/reference/distributed-project-leadership.rst +++ b/reference/distributed-project-leadership.rst @@ -119,9 +119,17 @@ DPL model & liaison duration DPL liaisons are assigned for a single release cycle. The assigned TC liaison will follow the project activities at regular intervals. Before the next cycle PTL election nominations start, the TC liaison will reset the project team -leadership model to PTL and the project team needs to opt-in to the DPL model -explicitly with the same or new liaisons. This requires +1 from all the people -volunteering as liaisons. +leadership model to PTL. A project team needs to opt-in to the DPL model +again, explicitly before the next cycle PTL election nominations start. This +can be done by either of the following options: + +* All current liaisons are recording their -1 vote against the change to reset + the leadership model. Once all liaisons have recorded -1 vote, the TC will + not reset the DPL model and will consider continuing the DPL model for the + next cycle as well. +* If the DPL model has already been reset, a new change to readopt the DPL + model needs to be proposed. This change requires +1 from all the people + volunteering as liaisons. Points of Concern -----------------