[wp-hackers] Finding a simple bug
sameers.public at gmail.com
Mon Jan 13 21:04:24 UTC 2014
Might it be easier to find bugs/issues for commonly-used plugins, that
might be better targets for first-timers?
I learned something by updating Wp-Footnotes to work in WP3 (thought it
turned out the original developer had already done it, I just didn't find
his Github repo before I found his WP.org repo.) But still, it was fun and
I learned a little bit of the WP API.
On Mon, Jan 13, 2014 at 12:51 PM, J.D. Grimes <jdg at codesymphony.co> wrote:
> Hi Manan,
> Yes WordPress is complex, so sometimes a bug can be hard to understand at
> first. I don’t think that there is a good way to find simple bugs at
> present. I think that there are plans to add a ‘good-first-bug’ tag to the
> bug tracker, so that simple bugs could be tagged with it. This would be
> helpful for new contributors I’m sure. I don’t think it has been done yet,
> On Jan 13, 2014, at 11:38 AM, manan shah <mananshah9328 at gmail.com> wrote:
> > Hi,
> > I am a newbie developer in word press , I know PHP and MYSQL very well .
> > wanted to contribute to WordPress by solving a bug . But due to big names
> > in a ticket in am not able to understand where to start.Can anyone guide
> > for finding a simple bug ?
> > - Manan
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers