It’s missing context, specifically, a clear definition of the PEP process you’re referring to. Also whether the plan is to clone the process and publish everything on a separate site, or if you intend to submit packaging PEPs to the Python SC for approval (and allow them to decide what criteria to use to approve them).
You probably also need to clearly define the scope of (what would currently be) PEPs you are going to take elsewhere. Changes that affect pip may impact the CPython distribution, and so probably need sign off from a CPython “representative” if you don’t want pushback when trying to update the version included with CPython (because someone thinks it’s a breaking change that isn’t appropriate for the 3.8.x or whatever release), while changes that only affect PyPI likely don’t - who decides for each not-a-PEP whether it’s in or out?
Providing that criteria or decision making process (or an intent to develop such a process) along with the question will give the SC something to actually respond to.