| From: |
| Guido van Rossum <guido-AT-python.org> |
| To: |
| python-committers <python-committers-AT-python.org> |
| Subject: |
| A different way to focus discussions |
| Date: |
| Fri, 18 May 2018 15:25:37 -0700 |
| Message-ID: |
| <CAP7+vJJ-BUjHjtDShnEKBWDe=vW_RwqfEZH4Um6yxcp=oAJAHw@mail.gmail.com> |
| Archive-link: |
| Article |
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.
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.
Thoughts? (We can dogfood this proposal too, if there's interest. :-)
--
--Guido van Rossum (python.org/~guido)