On Sun, Sep 2, 2018 at 9:32 AM, Nick Coghlan
I think the wider community cares more about "Is it in a PEP?" than you believe, as we had folks outright refusing to accept Description-Content-Type as legitimate when it was only defined in https://packaging.python.org/specifications/core-metadata/#description-conte..., with no PEP to back it up as being an officially endorsed interoperability standard.
Attempting to build legitimacy and credibility for a random collection of text files in a GitHub repo rather than continuing to use https://www.python.org/dev/peps/ feels like a pointless time-wasting distraction to me.
I think it's important to have a clear and unambiguous story for what counts as an official spec and what doesn't, but I doubt anyone cares whether it specifically involves PEPs or not. But if you're worried, we could write a PEP that says "python-dev hereby hands off packaging authority to the PyPA <link>, from now own their process is authoritative". -n -- Nathaniel J. Smith -- https://vorpus.org