[15:22:10] <cooperlees> I linked the main one in that .rst already
[15:29:47] <sumanah> cooperlees: ok, I've taken stuff from https://github.com/pypa/packaging-problems/issues/367 and I've turned it into a somewhat more detailed outline in the draft
[15:30:22] <cooperlees> I'll elaborate and trying include everyone else's points and start going over the API from what I know then I'll ask for people for anything I missed
[15:31:14] <cooperlees> sumanah: Feel free to be a so author - I'll feel you'll proof read it enough :D
[15:38:57] <sumanah> "The sponsor's job is to provide guidance to the PEP author to help them through the logistics of the PEP process (somewhat acting like a mentor)."
[15:40:25] <sumanah> the sponsor says stuff like "you should fix this bit before you submit" or "it's ready" or "use the mailing list, not just GitHub" or "here's what Type to use" etc
[15:52:43] <cooperlees> kk - I'll ask Lukasz as he use to proof read all my terrible english @ Facebook
[15:53:00] <cooperlees> (Even tho he's native language is Polski - Made me feel so bad ... haha)
[16:02:12] <sumanah> cooperlees: that could work .... Nick Coghlan might also be willing (he sponsored PEP 458)
[16:02:41] <sumanah> I have a call. back in a while
[16:06:36] <pradyunsg> cooperlees: basically a PEP Sponsor is a CPython Core Dev. It's a requirement to prevent random folks from asking for a PEP, for a thing that no one in the core team thinks is a good idea / worth documenting.
[16:07:17] <pradyunsg> It's a requirement for the process, to get a core developer to say "yea, that looks reasonable, I can help you out with the process" -- basically so that the folks maintaining the PEPs repository don't have a big headache all day. :)
[16:07:22] <cooperlees> I know this is hard to believe, but I'm not one to follow / love formalities :D
[16:09:26] <pradyunsg> cooperlees: well, if the PEP 609 saga goes well, packaging PEPs will get a significant reduction in the process, in that PyPA folks here would be able to fill that role of "PEP sponsor" than just the ones who are *also* CPython core devs. :)