[core-workflow] GSoC idea: bug.python.org improvements

[Nick Coghlan]

On 22 March 2015 at 23:16, Ezio Melotti <ezio.melotti at gmail.com> wrote:
> On Sun, Mar 22, 2015 at 9:50 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>> I did just remember another small item though - hooking up searching
>> by Real Name in addition to Username when adding someone to the nosy
>> list (not everyone uses the first.last naming convention for their
>> username, especially if they have an already established username
>> they're bringing over from other services)
>>
>
> That should already work, but the autocomplete only includes people in
> the expert list and committers.

Aye, that part is great, the specific part I'm referring to is the
search dialogue that pops up when you click on the "(list)" link.

I also wondered whether there might be a few enhancements that could
be gathered under a "Improved mentoring support" theme, like being
able to check how many patches someone has uploaded vs how many of the
related issues have been resolved, or helping mentors keep a record of
who's patches they've accepted recently.

At the moment we can track commits fairly well, but there isn't really
much of a link back to the uploaded patches outside the NEWS file and
commit message, which automated tools tend not to read. (We could also
look at using "hg commit -u" more to credit patch authors in the
metadata, and something
https://bitbucket.org/ede/committer/src/default/hgcommitter.py to
track the committer info. On the other hand, it may not be worth doing
that given the expected future work on forge.python.org based
workflows, regardless of whether that's Kallithea or Phabricator
based)

>>>   * since some of the Roundup devs said they would be available to
>>> help, one option would be to find a core Python mentor for this
>>> project (Nick?) and then the student can still interact with the
>>> Roundup guys (including me) and get help from other devs as well.
>>
>> I'm already trying to figure out how to gracefully hand at least some
>> of my current projects over to other people, so I won't be
>> volunteering for anything new any time soon :)
>
> If you figure that out let me know, or else I'll have to take the
> cloning route again :)

Taking into account the many things I'd like to eventually see fixed
upstream when figuring out what I want to do with my professional
career helps, but I can certainly see the attraction of the cloning
option :)

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia