openstack/governance
Code Issues Proposed changes

Update DPL model reset steps

Browse Source 
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
This commit is contained in:
Ghanshyam Mann
2024-08-07 15:06:48 -07:00
parent 7d97a0b2cd
commit 5bff5d1bac
1 changed files with 11 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
reference/distributed-project-leadership.rst
View File

@@ -119,9 +119,17 @@ DPL model & liaison duration
DPL liaisons are assigned for a single release cycle. The assigned TC liaison 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 will follow the project activities at regular intervals. Before the next cycle
PTL election nominations start, the TC liaison will reset the project team 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 leadership model to PTL. A project team needs to opt-in to the DPL model
explicitly with the same or new liaisons. This requires +1 from all the people again, explicitly before the next cycle PTL election nominations start. This
volunteering as liaisons. 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 Points of Concern
----------------- -----------------