interoperability-peps icon indicating copy to clipboard operation
interoperability-peps copied to clipboard

document how/when a PR here becomes a PEP?

Open qwcode opened this issue 10 years ago • 3 comments

document how/when a PR here takes it to the next step of becoming PEP in the PEP index.

who has to approve? based on what?

if we want people to try to write PEPs, they need to know how it moves along.

qwcode avatar Sep 15 '15 05:09 qwcode

@dstufft and I have access to create new ones directly (as does Paul Moore now), otherwise folks can follow the submission process in PEP 1.

There's also a matter of capturing the way we use the PEP process: https://mail.python.org/pipermail/distutils-sig/2015-September/026810.html

I'm now wondering if that might be better served by being captured on pypa.io rather than being a PEP.

ncoghlan avatar Sep 16 '15 06:09 ncoghlan

I've aimed to cover at least the basics of this in https://github.com/pypa/pypa.io/pull/12

(It's not enough to close this issue, but it's a start)

ncoghlan avatar Jan 21 '16 11:01 ncoghlan

Better reference for the process update: https://github.com/pypa/pypa.io/issues/11

ncoghlan avatar Jan 25 '16 02:01 ncoghlan