On Fri, Apr 26, 2019 at 7:18 PM Berker Peksağ <berker.pek...@gmail.com> wrote: > > 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. >
Recently Ernest migrated the tracker on a new machine, and he has been working on setting up a new test tracker. On the Roundup side, they have been working on porting Roundup to Python 3 and integrating the REST API we developed a few years ago with a GSoC student. I also submitted another GSoC proposal for this year with the goal of updating Roundup on b.p.o and writing tools that take advantage of the REST API (http://python-gsoc.org/psf_ideas.html). I was planning to write to python-committers and ask what features do we want to develop first, but I was already coordinating between Ernest, the Roundup folks, and GSoC admin/students so I was waiting to make sure things were viable before involving python-committers. On May 9 we will know for sure if we got a student, but things are currently looking good. I'm also aware of PEP 581 and the fact that we might eventually decide to abandon Roundup, however this work will still benefit Roundup and its users regardless of what we end up doing -- that's why I went ahead and submitted the proposal without discussing it with python-committers first. > 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. > The meta tracker at upfronthosting is gone for good, but nothing is lost, we have backups and can retrieve the patches if we need them. Best Regards, Ezio Melotti > --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/
