Amit Upadhyay wrote:
<rant>Consider http://code.djangoproject.com/ticket/398 for example. It looks like a good idea to me, patch is there, so is some discussion and suggestions, but activities ended 3 months back and from ticket there seems to be no idea if its being considered or what.
But publicising patches in a maillist won't push things forward because to be commited to the code the patch should be reviewed by core developers anyway. And reading about it in a maillist won't add them any free time :-).
Being a developer myself I use bug tracking as a sole source of thing to do because it's just so much more convenient than using many sources. If I see an interesting thing elsewhere I will file it to tracker for it to be completed some day. So filing it to bug tracker yourself is just more direct way of doing things. And if things don't go fast enough (as they always do :-) ) it's not because developers don't notice them, but because they're doing other things... from bug tracker :-).
Anyway I'm sure people writing patches for OSS projects know this very well. Just wanted to say something in support to lessen frustration :-)
