[Python-Dev] PEP 581: Using GitHub Issues for CPython

Nick Coghlan ncoghlan at gmail.com
Sat Mar 16 01:25:13 EDT 2019

On Fri, 8 Mar 2019 at 16:52, Karthikeyan <tir.karthi at gmail.com> wrote:
> Personally, I think more people will love it once they get to use it so if something like 100 issues can be migrated to a sample repo with labels, content etc.

We're already using GitHub issues for pretty much everything in Python
core development that *isn't* CPython itself, and even for CPython,
folks experience the core issue management interface in the overview
page for pull requests.

One of the requests we made at the Language Summit discussion last
year was for Mariatta to enhance PEP 581 with additional discussion of
what would need to change to bring the Roundup instance up to the
point of being competitive with the GitHub issues user experience,
which she added:

* https://www.python.org/dev/peps/pep-0581/#issues-with-roundup-bpo
* https://www.python.org/dev/peps/pep-0581/#why-not-focus-on-improving-roundup-bpo

There's been plenty of time since then for folks to put forward a
competing proposal to modernise the Roundup UI directly instead of
migrating to a different issue tracking tool, but so far no such
proposal has emerged.

One of the other blockers was the fact that the Contributor Licensing
Agreement process was tightly coupled to some custom fields in b.p.o
[1], and that is now very close to being resolved thanks to Mariatta's
efforts (and provides a nice workflow improvement in its own right).


[1] https://www.python.org/dev/peps/pep-0581/#update-the-cla-host

Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-Dev mailing list