[wp-hackers] Finding bugs to fix on Trac

[Lloyd Budd]

On 2/22/07, Ryan Boren <ryan at boren.nu> wrote:
> On 2/21/07, Jennifer Hodgdon <yahgrp at poplarware.com> wrote:
> > I was wondering, if someone wanted to contribute to the WordPress
> > effort by fixing some of the reported bugs, how would you suggest they
> > figure out which ones actually need fixing?
>
> First and foremost, fix whichever ones bother you.  We also do bug
> triage on the #wordpress-dev channel, and we occasionally have bug
> days on #wordpress-bugs.

Well said!

Emailing wp-hackers that you want to fix some bugs will also be very
positively received.

It would be great if the Contributing to Wordpress reflected this.


> > It seems like the best thing to do would be to design a new report
> > that actually checked if there were patch files associated with a bug
> > (should be possible, as the reports are just SQL statements, and the
> > patches must be in a table somewhere?)... but normal users cannot
> > create reports...

That sounds quite complicated, and would require attentional
infrastructure. Is it a patch or another file? Is it a complete patch
or a work in progress or a partial solution?


> We have a few keywords we use: commit, has-patch, dev-feedback,
> 2nd-opinion, needs-testing, reporter-feedback.

http://codex.wordpress.org/User:Foolswisdom/Trac_Keywords


> The various reports created from these are here:
>
> http://trac.wordpress.org/report

If a report needs revision or a different report is desired let me know.

Cheers,
Lloyd