Hi Venkatraman,
Venkatraman S wrote:
>
> On Tue, Feb 17, 2009 at 1:45 PM, "Martin v. Löwis" wrote:
>>
>> Don't expect too much
>> help from other people - I have been waiting for volunteers to show up
>> helping with the tracker for more than a year now.
>
> I have been mostly a silent spectator
> I have been mostly a silent spectator around and would like to chip in.
> Need some initial throttle(help) for the full-fledged attack :)
Please take a look at the meta tracker. It has various open issues, many
open for many months now. Please tackle one that can be fixed through
patches to the
On Tue, Feb 17, 2009 at 1:45 PM, "Martin v. Löwis" wrote:
> Don't expect too much
> help from other people - I have been waiting for volunteers to show up
> helping with the tracker for more than a year now.
>
I have been mostly a silent spectator around and would like to chip in.
Need some initi
On Tue, Feb 17, 2009 at 00:15, "Martin v. Löwis" wrote:
> > Let's improve the tracker UI to better fit our needs. Then, classify
> > them bugs and separate garbage from real development. Lastly, bug
> > reporters should get a better UI. That's it, any help is welcome.
>
> The plan sounds great.
> Let's improve the tracker UI to better fit our needs. Then, classify
> them bugs and separate garbage from real development. Lastly, bug
> reporters should get a better UI. That's it, any help is welcome.
The plan sounds great. I can help with the deployment aspects (reviewing
tracker patches,
This is the janitorial plan I mentioned earlier...
It's so humongously huge by now that I'm not sure whether I should
submit it to e.g. the Python Papers or just print it and set it on
fire and run screaming. Fortunately, a tl;dl summary is provided :)
Daniel
Summary
Let's improve the tracker UI
