osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[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/c58d32c33bd06eb386d3f33963a1434510528f68).
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20190304/166b6a50/attachment.html>