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

Carol Willing willingc at willingconsulting.com
Fri Mar 13 19:39:18 CET 2015


Hello Ezio and others,

Sorry about the blank message.

I'm happy to help informally for GSOC if needed. Rachel would be great 
as a supporting mentor (or whatever the correct wording is).

Thoughts on projects and focus are in line.

Thanks, Ezio, for mentoring :-)

Carol

On 13/03/2015 09:29, Brett Cannon wrote:
>
>
> My areas of focus would be:
>
> * workflow simplification in the issue tracker like what R. David 
> outlined previously
This one, while valuable, seems less focused for a student since likely 
there will be different opinions on the earlier outlined stuff by R. David.
> * Push button patch generation from a GitHub repo
This looks like a well bounded project for a student.
> * Some tool that will update a checkout (or somehow make sure a clone 
> is clean for patching), grab a patch from an issue, apply it, run the 
> test suite, and then ask if the committer wants to commit the patch 
> and submit it (assuming everything else worked out in favour of 
> committing the patch);
This looks like a good student project with valuable experience for the 
user.
> essentially script what the fancy workflows being proposed using 
> Phabricator/Kallithea do with the assumption the code was already 
> reviewed in the issue tracker and deemed worthy of being committed

>
>     Understanding in which direction we want to go will allow me to put
>     together a project that, once completed, will have long-term benefits
>     for our workflow.
>     Perhaps I should post this to python-dev too and get feedback from a
>     wider audience.
>
>
> If you want, but I would assume everyone who cares is here at least 
> for an initial discussion.
>
>
>     > Sure, we're likely to stop using Rietveld in favour of the winner of
>     > the forge.python.org <http://forge.python.org> analysis at some
>     point in the future, but that
>     > point is likely to be quite some time away where CPython is
>     concerned.
>     >
>
>     Having a student investigating how Kallithea and Phabricator will
>     interact with Roundup and start developing a proof-of-concept
>     integration and/or tools that we already know will be needed might
>     also be an idea.
>
>
> Yes, especially if I can make a decision fast enough to know which one 
> to focus on.
>
> -Brett
>
>     Best Regards,
>     Ezio Melotti
>
>     > Cheers,
>     > Nick.
>     >
>     > --
>     > Nick Coghlan   | ncoghlan at gmail.com <mailto:ncoghlan at gmail.com>
>      |   Brisbane, Australia
>
>
>
> _______________________________________________
> 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


-- 
*Carol Willing*
Developer | Willing Consulting
https://willingconsulting.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20150313/5719deb7/attachment.html>


More information about the core-workflow mailing list