> On May 18, 2018, at 3:25 PM, Guido van Rossum <gu...@python.org > <mailto:gu...@python.org>> wrote: > > Discussing PEPs on python-dev and python-ideas is clearly not scalable any > more. (Even python-committers probably doesn't scale too well. :-) > > I wonder if it would make sense to require that for each PEP a new GitHub > *repo* be created whose contents would just be a draft PEP and whose issue > tracker and PR manager would be used to debate the PEP and propose specific > changes. >
We have something similar for Project Jupyter. We have a jupyter-incubator org for third party projects that may someday be accepted into the Jupyter core. One repo in particular, https://github.com/jupyter-incubator/proposals <https://github.com/jupyter-incubator/proposals>, keeps track of all the currently active proposals with links out to their repos, if not hosted within the incubator org. > This way the discussion is still public: when the PEP-specific repo is > created the author(s) can notify python-ideas, and when they are closer to > submitting they can notify python-dev, but the discussion doesn't attract > uninformed outsiders as much as python-{dev,ideas} discussions do, and it's > much easier for outsiders who want to learn more about the proposal to find > all relevant discussion. > > PEP authors may also choose to use a different repo hosting site, e.g. > Bitbucket or GitLab. We can provide a script that allows checking the > formatting of the PEP easily (basically pep2html.py from the peps repo). > > Using a separate repo per PEP has the advantage that people interested in a > topic can subscribe to all traffic in that repo -- if we were to use the > tracker of the peps repo you would have to subscribe to all peps traffic. This makes sense - one repo per proposed PEP as PRs can be used to help iterate the wording and issues can focus on specific subtopics. Having one repo that acts as a landing page for all of the in-progress PEPs would help folks keep track of where an in-progress PEP is located. > > Thoughts? (We can dogfood this proposal too, if there's interest. :-) > > -- > --Guido van Rossum (python.org/~guido <http://python.org/~guido>) > _______________________________________________ > python-committers mailing list > python-committers@python.org <mailto:python-committers@python.org> > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/
_______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
