If you are confident enough the issue could be marked as resolved because it doesn't need a fix you can go ahead and "fix" it.
However, it's always recommended that you drop a line to current component mantainer to notify him about the changes, especially the first times you are contributing, thus he will be able to provide you some additional feedback. The mailing list is also a good starting point to point out tickets that doesn't need a fix. :) Thanks for your email, Simone On Sat, Mar 22, 2008 at 4:18 PM, Amr Mostafa <[EMAIL PROTECTED]> wrote: > Hi all, > > I want to help a bit on the issue tracker, and I wonder how far I should > go. I see that I've the permission to "resolve issues". Should I do that or > would be better to only comment on the issue and leave the actual resolving > to the component maintainer? Of course, I'm mainly talking about issues that > doesn't need a fix (i.e. Not an issue, can't reproduce, ...etc), because > otherwise the component maintainer will ultimately be needed to actually > commit the fix. > > Best, > - Amr >
