Skip to content

Commit

Permalink
PEP 1: PEP editors are pre-approved as sponsors (#2112)
Browse files Browse the repository at this point in the history
  • Loading branch information
gvanrossum authored Oct 19, 2021
1 parent 450f9f7 commit 56904fc
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion pep-0001.txt
Original file line number Diff line number Diff line change
Expand Up @@ -164,7 +164,8 @@ outlined below. Otherwise (i.e. none of the co-authors are core developers),
then the PEP author(s) will need to find a sponsor for the PEP.

Ideally, a core developer sponsor is identified, but non-core sponsors may also
be selected with the approval of the Steering Council. The sponsor's job is to
be selected with the approval of the Steering Council. Members of the GitHub
"PEP editors" team are pre-approved to be sponsors. The sponsor's job is to
provide guidance to the PEP author to help them through the logistics of the
PEP process (somewhat acting like a mentor). Being a sponsor does **not**
disqualify that person from becoming a co-author or PEP-Delegate later on (but
Expand Down

0 comments on commit 56904fc

Please sign in to comment.