<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Apr 26, 2019 at 10:26 AM Berker Peksağ <<a href="mailto:berker.peksag@gmail.com">berker.peksag@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, Apr 26, 2019 at 5:55 PM Guido van Rossum <<a href="mailto:guido@python.org" target="_blank">guido@python.org</a>> wrote:<br>
> - **Issue tracker:** We've discussed PEP 581, "Using GitHub Issues for<br>
>   CPython" by Mariatta Wijaya.  We're in favor of this move, and feel<br>
>   that the transition should be professionally planned and executed.<br>
>   In collaboration with the PSF we're exploring ideas on how to do<br>
>   that (using the successful roll-out of the new Warehouse<br>
>   infrastructure for PyPI as a model).<br>
<br>
I don't think there was a consensus on switching to GitHub Issues last<br>
time it was discussed. The most recent discussion about PEP 581 only<br>
has 12 messages. I think the council is making a premature decision<br>
here.<br>
<br>
I'm strongly against using GitHub Issues. I will change my mind once I<br>
see a sign that GitHub is actually listening to our feedback. We can't<br>
even get them to make the use of #NNNN and GH-NNNN in the commit title<br>
configurable (<a href="https://github.com/maintainers/early-access-feedback/issues/77" rel="noreferrer" target="_blank">https://github.com/maintainers/early-access-feedback/issues/77</a>)<br></blockquote><div><br></div><div>Because that repo is private I will say that the last comment on that issue was exactly a month ago from someone at GitHub saying that they are looking into this feature request.</div><div><br></div><div>-Brett<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
and have the ability to automatically strip intermediate commit<br>
messages from the commit message body<br>
(<a href="https://github.com/maintainers/early-access-feedback/issues/153" rel="noreferrer" target="_blank">https://github.com/maintainers/early-access-feedback/issues/153</a>) The<br>
only time I got a response from them was this:<br>
<a href="https://github.com/python/miss-islington/issues/16#issuecomment-396095622" rel="noreferrer" target="_blank">https://github.com/python/miss-islington/issues/16#issuecomment-396095622</a><br>
<br>
I volunteered to maintain our Roundup instance a while ago and already<br>
fixed some bugs: <a href="https://hg.python.org/tracker/python-dev/" rel="noreferrer" target="_blank">https://hg.python.org/tracker/python-dev/</a> I've also<br>
submit patches to improve UX and fix issues. I'd list list them here<br>
but I can't reach out to <a href="http://psf.upfronthosting.co.za/roundup/" rel="noreferrer" target="_blank">http://psf.upfronthosting.co.za/roundup/</a> at<br>
the moment. I hope the problem with the hosting is temporary because I<br>
have several non-trivial patches there.<br>
<br>
--Berker<br>
_______________________________________________<br>
python-committers mailing list<br>
<a href="mailto:python-committers@python.org" target="_blank">python-committers@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/python-committers" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/python-committers</a><br>
Code of Conduct: <a href="https://www.python.org/psf/codeofconduct/" rel="noreferrer" target="_blank">https://www.python.org/psf/codeofconduct/</a><br>
</blockquote></div></div>