<div dir="ltr">That sounds great. Would you be interested in an apprentice mentor? I haven't done any python core dev work (yet) but I'm an engineer and I've mentored plenty of interns before and enjoy it. </div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 12, 2015 at 11:12 AM, Ezio Melotti <span dir="ltr"><<a href="mailto:ezio.melotti@gmail.com" target="_blank">ezio.melotti@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
Since the PSF is looking for ideas and mentors for Google Summer of<br>
Code, I was thinking about proposing and mentoring a project that aims<br>
at further improving our bug tracker.<br>
<br>
I'm writing to core-workflow in order to understand what features we<br>
want and which ones have higher priority, so that I can put together a<br>
coherent proposal.<br>
<br>
There are currently two PEPs that are proposing changes to our infrastructure:<br>
* PEP 462 - Core development workflow automation for CPython<br>
(<a href="https://www.python.org/dev/peps/pep-0462/" target="_blank">https://www.python.org/dev/peps/pep-0462/</a>)<br>
* PEP 474 - Creating <a href="http://forge.python.org" target="_blank">forge.python.org</a><br>
(<a href="https://www.python.org/dev/peps/pep-0474/" target="_blank">https://www.python.org/dev/peps/pep-0474/</a>)<br>
<br>
These proposals will likely require changes to the bug tracker if we<br>
want to have a solid integration with the new tools and they might<br>
make for a good project, however it might still be too early to know<br>
what we will actually need.<br>
<br>
There are other changes that have been proposed in the past, in particular:<br>
* Some features previously discussed on this ML and summarized at<br>
<a href="https://wiki.python.org/moin/TrackerDevelopmentPlanning" target="_blank">https://wiki.python.org/moin/TrackerDevelopmentPlanning</a><br>
* Some other miscellaneous features listed at<br>
<a href="https://wiki.python.org/moin/DesiredTrackerFeatures" target="_blank">https://wiki.python.org/moin/DesiredTrackerFeatures</a><br>
* Better integration with Rietveld (e.g. add messages to roundup<br>
when someone posts a review)<br>
* Smarter branch detection in patches (sometimes patches don't get<br>
the review link)<br>
* Patch analysis (information such as affected files could be<br>
extracted from the files and used by Roundup)<br>
* Reviewing and applying patches submitted on the meta-tracker<br>
* Fix other issues listed on the meta-tracker<br>
<br>
These (or a subset of these) might also make for a good project,<br>
albeit less focused.<br>
<br>
After discussing with Nick on IRC about this, I also sent an email to<br>
roundup-devel about another possible project to be developed by<br>
Roundup under the umbrella of the PSF: adding a RESTful interface (see<br>
<a href="http://issues.roundup-tracker.org/issue2550734" target="_blank">http://issues.roundup-tracker.org/issue2550734</a>). This will also help<br>
us with any future work might want to do to integrate our bug tracker<br>
with other tools.<br>
<br>
If you have any feedback let me know.<br>
<br>
Best Regards,<br>
Ezio Melotti<br>
_______________________________________________<br>
core-workflow mailing list<br>
<a href="mailto:core-workflow@python.org">core-workflow@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/core-workflow" target="_blank">https://mail.python.org/mailman/listinfo/core-workflow</a><br>
This list is governed by the PSF Code of Conduct: <a href="https://www.python.org/psf/codeofconduct" target="_blank">https://www.python.org/psf/codeofconduct</a><br>
</blockquote></div><br></div>