[wp-hackers] Finding bugs to fix on Trac

Jennifer Hodgdon yahgrp at poplarware.com
Wed Feb 21 14:29:03 GMT 2007

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?

On the "Contributing to Wordpress" page in the Codex, there's a link 
to a page listing some To Dos, but it's totally out of date.

In Trac, there is a report that purports to tell which bugs need 
patches, but it's going off keywords, and practically none of the bugs 
have the right keywords in them, so the report basically is listing 
all the bugs marked "new", whether or not they have patches. There 
also doesn't seem to be any bug status that would reflect that someone 
thinks it is a bug, but it doesn't have a patch.

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...

Thoughts? Is there some searching mechanism I am missing?


More information about the wp-hackers mailing list