[core-workflow] bugs.python.org-related GSoC project

[Brett Cannon]

Another idea would be dropping Rietveld for some other code review tool.
Guido has mentioned we should probably switch off since our copy of
Rietveld no longer tracks upstream.

On Thu, Mar 12, 2015 at 2:12 PM Ezio Melotti <ezio.melotti at gmail.com> wrote:

> Hi,
> Since the PSF is looking for ideas and mentors for Google Summer of
> Code, I was thinking about proposing and mentoring a project that aims
> at further improving our bug tracker.
>
> I'm writing to core-workflow in order to understand what features we
> want and which ones have higher priority, so that I can put together a
> coherent proposal.
>
> There are currently two PEPs that are proposing changes to our
> infrastructure:
>     * PEP 462 - Core development workflow automation for CPython
> (https://www.python.org/dev/peps/pep-0462/)
>     * PEP 474 - Creating forge.python.org
> (https://www.python.org/dev/peps/pep-0474/)
>
> These proposals will likely require changes to the bug tracker if we
> want to have a solid integration with the new tools and they might
> make for a good project, however it might still be too early to know
> what we will actually need.
>
> There are other changes that have been proposed in the past, in particular:
>     * Some features previously discussed on this ML and summarized at
> https://wiki.python.org/moin/TrackerDevelopmentPlanning
>     * Some other miscellaneous features listed at
> https://wiki.python.org/moin/DesiredTrackerFeatures
>     * Better integration with Rietveld (e.g. add messages to roundup
> when someone posts a review)
>     * Smarter branch detection in patches (sometimes patches don't get
> the review link)
>     * Patch analysis (information such as affected files could be
> extracted from the files and used by Roundup)
>     * Reviewing and applying patches submitted on the meta-tracker
>     * Fix other issues listed on the meta-tracker
>
> These (or a subset of these) might also make for a good project,
> albeit less focused.
>
> After discussing with Nick on IRC about this, I also sent an email to
> roundup-devel about another possible project to be developed by
> Roundup under the umbrella of the PSF: adding a RESTful interface (see
> http://issues.roundup-tracker.org/issue2550734).  This will also help
> us with any future work might want to do to integrate our bug tracker
> with other tools.
>
> If you have any feedback let me know.
>
> Best Regards,
> Ezio Melotti
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20150313/302163c6/attachment.html>