Skip to content

Commit 35d53a8

Browse files
PEP 1: Add 'Finding a sponsor' heading (#5201)
Co-authored-by: Stan Ulbrych <stan@python.org>
1 parent 1d89cdd commit 35d53a8

1 file changed

Lines changed: 6 additions & 2 deletions

File tree

‎peps/pep-0001.rst‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -157,8 +157,8 @@ PEP to make properly formatted, of high quality, and to address
157157
initial concerns about the proposal.
158158

159159

160-
Submitting a PEP
161-
----------------
160+
Finding a sponsor
161+
-----------------
162162

163163
Following the above initial discussion, a *sponsor* must be found for the PEP.
164164
If one or more of the PEP's co-authors qualify as a sponsor, they are responsible
@@ -179,6 +179,10 @@ sponsor does **not** disqualify that person from becoming a co-author or
179179
PEP-Delegate later on. The sponsor of a PEP is recorded in the
180180
"Sponsor:" field of the header.
181181

182+
183+
Submitting a PEP
184+
----------------
185+
182186
Once the sponsor or the core developer(s) co-authoring the PEP deem the PEP
183187
ready for submission, the proposal should be submitted as a draft PEP via a
184188
`GitHub pull request`_. The draft must be written in PEP style as described

0 commit comments

Comments
 (0)