From 49398ad0f78e6399893885206f771d90b0c2afca Mon Sep 17 00:00:00 2001 From: Stan Ulbrych Date: Mon, 21 Sep 2026 17:48:50 +0100 Subject: [PATCH 1/2] Update PSRT inactivity policy --- security/psrt.csv | 2 +- security/psrt.rst | 9 ++++++--- 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/security/psrt.csv b/security/psrt.csv index f6dff2073..b7f283ac8 100644 --- a/security/psrt.csv +++ b/security/psrt.csv @@ -15,7 +15,7 @@ Jelle Zijlstra,JelleZijlstra, Kushal Das,kushaldas, Kirill Podoprigora,eclips4, Larry Hastings,larryhastings, -Łukasz Langa,ambv,Release Manager +Łukasz Langa,ambv, Ned Deily,ned-deily,"Admin, Release Manager" Pablo Galindo Salgado,pablogsal,Release Manager Paul McMillan,paulmcmillan, diff --git a/security/psrt.rst b/security/psrt.rst index c2a98eff2..0c1e4b7e1 100644 --- a/security/psrt.rst +++ b/security/psrt.rst @@ -32,14 +32,17 @@ The nomination succeeds if the nomination receives at least two-thirds positive votes from a vote of existing PSRT members that is open for one week and not vetoed by the Steering Council. -Once per year the Steering Council will receive a report of inactive members -of the PSRT with the recommendation to remove the inactive users from the PSRT. +Every six months the Steering Council will receive a report of inactive PSRT +members with the recommendation to remove the inactive users from the PSRT. “Inactive” is defined as a member who hasn’t coordinated or commented on a -vulnerability report in the past year since the last report was generated. +vulnerability report in the past six months since the last report was generated. The Steering Council may remove members of the PSRT with a simple vote. Members of the PSRT who are a Release Manager or Steering Council member may remain in the PSRT regardless of inactivity in vulnerability reports. +When a Release Manager's term ends, their PSRT membership becomes a regular +membership subject to the inactivity policy above. PSRT admins are not exempt +from the inactivity policy and are included in the report of inactive members. .. _similar to core team nominations: https://devguide.python.org/core-team/join-team/ From 7d698dd74389a2025a11e0117470b4ee5410453f Mon Sep 17 00:00:00 2001 From: Stan Ulbrych Date: Tue, 22 Sep 2026 18:24:54 +0100 Subject: [PATCH 2/2] Clarify more things around release team membership --- security/psrt.rst | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/security/psrt.rst b/security/psrt.rst index 0c1e4b7e1..b338c37f2 100644 --- a/security/psrt.rst +++ b/security/psrt.rst @@ -38,11 +38,13 @@ members with the recommendation to remove the inactive users from the PSRT. vulnerability report in the past six months since the last report was generated. The Steering Council may remove members of the PSRT with a simple vote. -Members of the PSRT who are a Release Manager or Steering Council member may -remain in the PSRT regardless of inactivity in vulnerability reports. -When a Release Manager's term ends, their PSRT membership becomes a regular -membership subject to the inactivity policy above. PSRT admins are not exempt -from the inactivity policy and are included in the report of inactive members. +Release Managers must be members of the PSRT for the duration of their term. +Steering Council members and the release team experts may join the PSRT if they +wish. All of these members may remain in the PSRT regardless of inactivity in +vulnerability reports. When a member leaves these roles, their PSRT membership +becomes a regular membership subject to the inactivity policy above. +PSRT admins are not exempt from the inactivity policy and are included in the +report of inactive members. .. _similar to core team nominations: https://devguide.python.org/core-team/join-team/