On 21 March 2015 at 17:29, Jørn Lomax <[email protected]> wrote:
>
>
> On 21.03.2015 00:23, Ezio Melotti wrote:
>>
>> On Fri, Mar 20, 2015 at 7:12 PM, Jørn Lomax <[email protected]> wrote:
>>>
>>> Hi
>>>
>>> I'm a potential GSoC participant, and I'm interested in the bug tracker
>>> improvement idea[1]. I had a brief look at what has already been
>>> discussed
>>> on the mailing list and liked what I read.
>>>
>>> I don't know anything about the code-review tools mentioned (Kallithea
>>> and
>>> Phabricator), but I would  be up to investigating how they could be
>>> integrated. But I really like the idea of integrating a REST API to
>>> roundup,
>>> but I'm not sure if that would be a python-core project or a distinct
>>> roundup project (requireing mentors from the Roundup devs)?
>>>
>> Adding a REST API to Roundup would be a separate project, and it's
>> currently being discussed on the roundup-devel ML
>> (http://sourceforge.net/p/roundup/mailman/roundup-devel/).
>> No one volunteered to mentor the project yet, but maybe someone will
>> step forward if they see interested students.
>>
>> Best Regards,
>> Ezio Melotti
>>
>>> But I'm very interested in doing a project with the python core team, so
>>> if
>>> there are any other interesting ideas I'm definalty up to it. I should
>>> perhaps ask around on the python-dev ML?
>>>
>>> [1]https://wiki.python.org/moin/SummerOfCode/2015/python-core
>
> So is there any of the ideas discussed for bug.python.org you think might be
> a viable GSoC project?

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
fair to ask a GSoC student to do that without a mentor that was
already part of the upstream Roundup community that could facilitate
getting their patches to a point where they were ready to be merged.

Regards,
Nick.


-- 
Nick Coghlan   |   [email protected]   |   Brisbane, Australia
_______________________________________________
core-workflow mailing list
[email protected]
https://mail.python.org/mailman/listinfo/core-workflow
This list is governed by the PSF Code of Conduct: 
https://www.python.org/psf/codeofconduct

Reply via email to