On Sun, 8 Dec 2019 at 20:39, Paul Moore <p.f.mo...@gmail.com> wrote: > On Sun, 8 Dec 2019 at 09:00, Nick Coghlan <ncogh...@gmail.com> wrote: > > For pre-PEPs, the approach I now like is to make a local PR in my *fork* of > > the PEPs repo. Then I'll only change it into a PR against the main repo > > when it's time to assign a PEP number. > > Using PRs to manage the development of a PEP, whether leading up to > submission or after initial submission, is fine. But I strongly prefer > discussions on the content of a PEP to be handled in the actual > discussion forum (mailing lists or Discourse).Too many people with an > interest in the subject are likely to miss discussions happening on > PRs.
Aye, definitely - the cases where I've taken this approach have been ones where I had co-authors, so we were discussing low level details from really early on, and the PR served as the venue for coming to an internal agreement amongst the co-authors before presenting the shared proposal to everyone else. It's not a substitute for the broader PEP review and discussion process, but I do believe it can help reduce some of the noise in that broader discussion (since low level clarifications can be kept separate from the more conceptual reviews). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/N2V6AFTPLCRG7LE6TCIHGS2SPKYY6FEJ/ Code of Conduct: http://python.org/psf/codeofconduct/
