[wp-hackers] Code reviews for plugins?

Lox lox.dev at knc.nc
Sun Aug 22 02:17:28 UTC 2010

What about starting with a reviewed best practices code snippets database?

It will allow developers to use them and make *better plugins easier to
review*. That could be a butch of scripts organized in folders as a (for
example) a github project reviewed using gerrit. We would easily display
them on the web, then.

2010/8/20 24/7 <24-7 at gmx.net>

> On 19 Aug., 23:12, "Heiko Rabe" <heiko.r... at code-styling.de> wrote:
> > During this time delay a well done plugin will be presented to audience
> as a
> > "bad" one, which is wrong but felt so by audience for psychological
> reasons.
> > Keep in mind, that this affects also the download and utilization rates
> of
> > plugins!
> I guess you could just look at the (not that old) theme-reviewers list
> (or as joseph scott) and the threads that were about the review
> process. They had a hard time in the beginning with a lot of themes
> stuck in the queue waiting for their review. As far as i remember they
> found some ways to optimize the process. Maybe it's a good starting
> point.
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

lox.dev at knc.nc

More information about the wp-hackers mailing list