[python-committers] A different way to focus discussions
Serhiy Storchaka
storchaka at gmail.com
Sat May 19 02:52:14 EDT 2018
19.05.18 01:25, Guido van Rossum пише:
> 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.
>
> 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).
What will happen with these repos after accepting or rejecting
corresponding PEPs?
More information about the python-committers
mailing list