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

Ezio Melotti ezio.melotti at gmail.com
Mon Mar 16 18:27:35 CET 2015


On Mon, Mar 16, 2015 at 6:37 PM, Saimadhav Heblikar
<saimadhavheblikar at gmail.com> wrote:
> On 16 March 2015 at 21:06, Barry Warsaw <barry at python.org> wrote:
>> On Mar 16, 2015, at 09:52 PM, Nick Coghlan wrote:
>>
>>>I've found one neat trick for this kind of scenario is to devise
>>>standalone projects that are likely to be useful regardless of what
>>>happens in the broader context. REST-API-in-upstream-Roundup
>>>qualifies
>>
>
> Hi,
>
> I am currently looking at the design of Roundup[1]. Would a standalone
> project as mentioned above be bugs.python.org roundup specific or
> would it target upstream?

Upstream.  I sent a mail to roundup-devel asking if anyone wants to
mentor the project but no one stepped forward.  If you would like to
tackle this project you could write there -- maybe someone will
volunteer as a mentor once they see students are willing to work on
it.

> Which would serve *us* better?

Once it's committed upstream we can easily pull it and use it right away.

> In either case, would someone familiar with bugs.python.org roundup
> point me to the differences between bugs.python.org from the upstream
> version?(if any)

Here is our Roundup clone: https://hg.python.org/tracker/roundup/
There are a few minor differences that are kept in a separate branch
called "python-dev".  Eventually these differences should either be
ported upstream or removed altogether, but no one had time to do it
yet.

bugs.python.org is a specific instance of Roundup and the code is at
https://hg.python.org/tracker/python-dev/
You can also find more info at https://wiki.python.org/moin/TrackerDevelopment

Best Regards,
Ezio Melotti

>
> [1] - http://roundup.sourceforge.net/docs/design.html
>
>
>
> --
> Regards
> Saimadhav Heblikar
> _______________________________________________
> 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


More information about the core-workflow mailing list