On Apr 26, 2019, at 09:12, Berker Peksağ <berker.peksag@gmail.com> wrote:
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.
Technically speaking, the PEP is still in Draft state. I have a PR up for splitting the migration into two separate PEPs, one for the rationale and a second one for the migration plan:
https://github.com/python/peps/pull/1013
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
It would be very helpful if you could add these comments to the PR.
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.
And as a fan of Roundup and its critical importance to the Python development process, I want to personally thank you for all your —and everyone who has contributed to it over the years— hard work in maintaining it.
Cheers, -Barry