On Sun, Mar 17, 2013 at 4:28 AM, R. David Murray <rdmur...@bitdance.com>wrote:
> On Sun, 17 Mar 2013 02:56:12 +0300, anatoly techtonik <techto...@gmail.com> > wrote: > > The major goal is to lower the barrier to let people start hacking at > > Roundup. The secondary goal it to I am not sure about the Python 3 > porting, > > but currently b.p.o uses a patched version of Roundup, which is no good. > If > > something is useful for b.p.o - it should be shared with Roundup > community > > too. > > I believe Ezio has filed all his new patches that are applicable > upstream, some of which have been taken up. I'm not sure of the status > of the older patches, I haven't looked at what they are. b.p.o still uses patched version of Roundup while with a full upstream commit access it should use standard version. And these are buried inside version control history. These should be stored as a patch queue until merged or until there is a API to transform them into Roundup extensions. > > We've made a somewhat detailed plan at > > http://piratepad.net/bugs-python-org- would be nice to see > > bugs.python.org among Sprint projects - > > https://us.pycon.org/2013/community/sprints/ > > It's a bit too late to propose that, I think. Ezio isn't here, I'm > leading the Core sprint, and Martin I suspect has his own plans for the > sprint (I'm not sure how long he is staying). I don't think there is > anyone else who would even think about doing it. It doesn't look like > anyone is sprinting on roundup itself. We need to recruit more people then. I am sure there are many people out there who are interested to help. Should we concentrate on outreach website instead? =) -- anatoly t.
_______________________________________________ Tracker-discuss mailing list Tracker-discuss@python.org http://mail.python.org/mailman/listinfo/tracker-discuss
