From 712207bba3b63936a3cf3c4f23042c79cdb25ef4 Mon Sep 17 00:00:00 2001 From: Barry Warsaw Date: Wed, 16 Apr 2025 16:28:49 -0700 Subject: [PATCH] A few minor clarifications about the new developer process --- core-developers/become-core-developer.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/core-developers/become-core-developer.rst b/core-developers/become-core-developer.rst index 739792b48..70b7e25af 100644 --- a/core-developers/become-core-developer.rst +++ b/core-developers/become-core-developer.rst @@ -38,10 +38,12 @@ are granted through these steps: #. If the candidate receives at least two-thirds positive votes when the poll closes (as per :pep:`13`), the submitter `emails the steering council `_ with the candidate's email address - requesting that the council either accept or reject the proposed membership. + requesting that the council either accept or reject the proposed membership. Technically, the + council may only `veto a positive vote `_. -#. Assuming the steering council does not object, a member of the council or delegate - (approver) will email the candidate: +#. Assuming the steering council does not veto the positive vote, a member of the council or its + delegate (approver, usually in practice a :ref:`Developer-in-Residence `) will + email the candidate: - A request for account details as required by `🔒 python/voters `_.