[Python-Dev] PEPs from non-core devs now need a sponsor (original) (raw)

Alex Walters tritium-list at sdamon.com
Fri Mar 8 08:09:11 EST 2019

I'm confused about this. Didn't you need someone with merge permissions already to merge a pep into the pep repo? Isn't this just adding a layer of paperwork to something that was already the case for all practical purposes?

-----Original Message----- From: Python-Dev <python-dev-bounces+tritium-_ _list=sdamon.com at python.org> On Behalf Of Brett Cannon Sent: Monday, March 4, 2019 8:44 PM To: python-dev <python-dev at python.org> Subject: [Python-Dev] PEPs from non-core devs now need a sponsor

The steering council has implemented a new idea called sponsors to the PEP process (added in https://github.com/python/peps/commit/c58d32c33bd06eb386d3f33963a14 34510528f68). The thinking is that to help make sure PEPs from non-core developers receive appropriate guidance through the PEP process, a core developer needs to sign on to be a sponsor of the PEP. Being a sponsor does not preclude the core dev from eventually becoming a co-author or BDFL- delegate later on (but obviously not both), but the expectation is the sponsor is supportive of the idea (because if a single core dev won't sign on to help then what chance does the PEP have of being accepted?).

If this doesn't turn out well we can obviously revert this, but hopefully this will make things smoother for those who are new to the PEP process.

More information about the Python-Dev mailing list