Movatterモバイル変換
[0]ホーム
[Python-Dev] PEP 581: Using GitHub Issues for CPython
Nick Coghlanncoghlan 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 Pythoncore development that *isn't* CPython itself, and even for CPython,folks experience the core issue management interface in the overviewpage for pull requests.One of the requests we made at the Language Summit discussion lastyear was for Mariatta to enhance PEP 581 with additional discussion ofwhat would need to change to bring the Roundup instance up to thepoint 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-bpoThere's been plenty of time since then for folks to put forward acompeting proposal to modernise the Roundup UI directly instead ofmigrating to a different issue tracking tool, but so far no suchproposal has emerged.One of the other blockers was the fact that the Contributor LicensingAgreement 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'sefforts (and provides a nice workflow improvement in its own right).Cheers,Nick.[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-Devmailing list
[8]ページ先頭