From e783b307ea1e3cf029a6e5a37da9140db4a50a56 Mon Sep 17 00:00:00 2001 From: Chris Dent Date: Fri, 10 Aug 2018 16:10:12 +0100 Subject: [PATCH] Add a house rule about how to signal appointed PTLs We've been dealing with how to make appointed PTLs official and documented in a rather ad hoc fashion: something different each cycle. This change provides a house rule which puts the responsibility and the documentation in the combined hands of the appointed PTL and the TC that appointed them and not election handling (where it doesn't make sense since no election happened). Change-Id: Idf78e00c59d10528a2b4950f8baa93c6731973ea --- reference/house-rules.rst | 21 +++++++++++++++++++ ...ctions-process-for-leaderless-programs.rst | 3 +++ 2 files changed, 24 insertions(+) diff --git a/reference/house-rules.rst b/reference/house-rules.rst index c0ed83408..726f77896 100644 --- a/reference/house-rules.rst +++ b/reference/house-rules.rst @@ -72,6 +72,24 @@ If a TC member feels that one of these responses needs to be discussed by the entire TC, they should bring it up on the mailing list and the change should not be approved until after the discussion is completed. +Appointing PTLs +--------------- + +In a resolution regarding :ref:`leaderless programs`, the TC was granted +authority to appoint a Project Team Lead to any official project where the +`election`_ process failed to produce a leader. When this happens, +``reference/projects.yaml`` in the ``governance`` repository should be updated +to indicate the new PTL and their appointment by adding their name and contact +details and updating an ``appointed`` key with the cycle during which they will +be the PTL. If the ``appointed`` key is already present, add the cycle to the +list. If the key is not present, add it and set the cycle as a single member of +a list. This format is used for two reasons: to track all the cycles for which +there has been an appointment and to require a comprehensible change for review +by the TC. The ``appointed`` key should only be changed when the PTL was not +chosen by the election process. + +These changes are subject to the standard review and approval guidelines. + Rolling back fast-tracked changes --------------------------------- @@ -79,3 +97,6 @@ As a safety net, if any member disagrees with any change that was fast-tracked under one of those house rules, that member can propose a revert of the change. Such revert should be directly approved by the chair and the change be discussed on the mailing list or on the re-proposed change in gerrit. + + +.. _election: http://docs.openstack.org/project-team-guide/open-community.html#technical-committee-and-ptl-elections diff --git a/resolutions/20141128-elections-process-for-leaderless-programs.rst b/resolutions/20141128-elections-process-for-leaderless-programs.rst index 419941c01..d9b8ad499 100644 --- a/resolutions/20141128-elections-process-for-leaderless-programs.rst +++ b/resolutions/20141128-elections-process-for-leaderless-programs.rst @@ -1,3 +1,6 @@ + +.. _leaderless programs: + =========================================== 2014-11-28 Process for Leaderless Programs ===========================================