On Fri, Apr 26, 2019 at 5:55 PM Guido van Rossum <gu...@python.org> wrote: > - **Issue tracker:** We've discussed PEP 581, "Using GitHub Issues for > CPython" by Mariatta Wijaya. We're in favor of this move, and feel > that the transition should be professionally planned and executed. > In collaboration with the PSF we're exploring ideas on how to do > that (using the successful roll-out of the new Warehouse > infrastructure for PyPI as a model).
I don't think there was a consensus on switching to GitHub Issues last time it was discussed. The most recent discussion about PEP 581 only has 12 messages. I think the council is making a premature decision here. I'm strongly against using GitHub Issues. I will change my mind once I see a sign that GitHub is actually listening to our feedback. We can't even get them to make the use of #NNNN and GH-NNNN in the commit title configurable (https://github.com/maintainers/early-access-feedback/issues/77) and have the ability to automatically strip intermediate commit messages from the commit message body (https://github.com/maintainers/early-access-feedback/issues/153) The only time I got a response from them was this: https://github.com/python/miss-islington/issues/16#issuecomment-396095622 I volunteered to maintain our Roundup instance a while ago and already fixed some bugs: https://hg.python.org/tracker/python-dev/ I've also submit patches to improve UX and fix issues. I'd list list them here but I can't reach out to http://psf.upfronthosting.co.za/roundup/ at the moment. I hope the problem with the hosting is temporary because I have several non-trivial patches there. --Berker _______________________________________________ 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/
