PEP 609: amend to allow for funding votes

peps/pep-0609.rst

@@ -71,6 +71,8 @@ Goals
 The following section formalizes the goals (and non-goals) of the PyPA
 and this governance model.
 
+.. _`PyPA's goals`:
+
 Goals of the PyPA
 -----------------
 
@@ -216,6 +218,33 @@ Removal of a project from PyPA
 
 Proposing the removal of a project in the PyPA organization.
 
+Approval for disbursement of PyPA funds
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Proposing the use of PyPA funds to pay for project development,
+maintenance, or any other activity that advances the :ref:`PyPA's goals`.
+
+Proposals for funds must, at the bare minimum, include:
+
+- A specific dollar amount, either as a fixed sum or as an ongoing
+  expense
+- A clear rationale for why PyPA funding is being sought out and
+  and how this aligns with the PyPA's stated goals
+- An overview of how the funds are going to be spent
+- Evidence of support from committers of the PyPA project(s) seeking
+  funding
+
+It is recommended that PyPA members connect with PSF Accounting before
+putting forward a funding proposal. They can provide information on:
+
+- PyPA's current balance
+- The legal requirements before funds can be disbursed
+
+As the PyPA is a fiscal sponsoree of the Python Software Foundation,
+PyPA's funds are owned and managed by the PSF. All expenses are
+ultimately subject to final approval by the PSF, in accordance to PyPA's
+fiscal sponsorship agreement.
+
 Updates to the Governance/Specification Processes
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -253,6 +282,10 @@ incidents involving their projects, PyPA members are expected to
 report those incidents up to `the PSF Conduct WG`_, for recording
 purposes and for potential assistance.
 
+History of amendments
+=====================
+
+* 2026-03-23: Permit committer votes for the use of PyPA funds
 
 References
 ==========