On 06:44 pm, eprparadocs@gmail.com wrote:
Let me know if I can help out...either triaging the tickets or fixing the 'easier' things right now.
I thought that's what I was doing :). Don't worry about trying to triage controversial or confusing stuff, or reprioritize too much; just closing the obvious duplicates and reassigning things that have their component set blatantly wrong would be a lot of help. And of course, *any* ticket that you want to steal and fix would be fine.
On 6/28/07, glyph@divmod.com <glyph@divmod.com> wrote:
According to the Twisted tracker, I currently have 142 tickets.
Many of these are simply because I'm the default assignee of the default "core" component, so almost all new tickets end up in my list.
It's getting to the point where I don't even have time to triage all the tickets assigned to me, let alone work on them.
If anyone is looking for stuff to do to help out Twisted, triaging all of the 'normal', 'core' tickets assigned to me would be a big help. Not only would it circulate tickets to more appropriate people to be working on them than me, it will also generally make me feel less discouraged when I look at the apparently infinite amount of work I have to do.
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python