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

[Ezio Melotti]

On Sat, Mar 21, 2015 at 9:33 PM, R. David Murray <rdmurray at bitdance.com> wrote:
> On Sat, 21 Mar 2015 23:13:13 +1000, Nick Coghlan <ncoghlan at gmail.com> wrote:
>> I don't think we've discussed it anywhere yet (unless I mentioned it
>> to Ezio on IRC), but there are some issues around dependency display
>> that could conceivably be handled downstream. The main one is showing
>> which bugs a given bug is *blocking* - that is, those which depend on
>> the bug you're currently looking at.
>>
>> Another nice-to-have from my perspective would be the ability to add a
>> new comment without having to scroll back to the top of the
>> discussion.
>>
>> Unfortunately, I suspect those would also qualify as being projects
>> best tackled under the Roundup banner, and I don't think it would be
>
> Nope.  Both of those are instance-only modifications, not core Roundup.
> The 'dependencies' field doesn't even exist in the stock roundup
> instance template.
>
> Comment box at the bottom has been previously suggested and was
> rejected in favor of hotkeys that let you scroll back and forth easily.
> I think that decision could be revisited, though.
>

FTR, you can press 'r' (for reply) to jump to the reply box at the
top, 'esc' to unfocus it, and 'l' (lowercase L, for last) to jump to
the last message.
There are other shortcuts that you can see by pressing '?' or by
clicking 'Keyb. shortcuts (?)' at the end of the sidebar.  Note that
these shortcuts only work in the issues pages.

> Both of these are "small" modifications, so you'd need a bunch
> of additional items to make it a GSoC project.  And, you need a
> mentor...that really seems to be the sticking point right now.
> I myself will simply have no time this summer to do it, otherwise
> I would.
>

I've been talking with a few people and this seems to be the situation
right now:

  * There is the bugs.python.org project that I suggested and that I'm
willing to mentor, and some students already showed interest (so I
would advise them to also have a backup project in case they don't get
accepted for this);
  * since there are several things that can be fixed/improved and none
of them seems to have an particularly high priority, I think they can
be decided together with the students (different students might prefer
to work on different ideas in different order, and that shouldn't
matter as long as they do enough work).

  * There is the Roundup project about adding a REST API that has been
proposed upstream, however no Roundup mentor has stepped forward;
  * 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.

Best Regards,
Ezio Melotti

> --David