[wp-hackers] Code reviews for plugins?
Philip M. Hofer (Frumph)
philip at frumph.net
Wed Aug 25 07:28:10 UTC 2010
I would like to see the 'works' 'doesn't work' that is implemented on each
plugin page to be scanned through and if a certain amount of doesn't work is
found then it can be recommended for removal.
I would rather this be looked at further then any time-lines or version
releases of wordpress used as a basis.
----- Original Message -----
From: "Rich Pedley" <elfin at elfden.co.uk>
To: <wp-hackers at lists.automattic.com>
Sent: Wednesday, August 25, 2010 12:21 AM
Subject: Re: [wp-hackers] Code reviews for plugins?
> On 25/08/2010 05:42, Otto wrote:
>> I'd like everybody discussing this to keep in mind that there is a
>> very large difference between "review" and "approval".
> in which case the user reviews that appear on the plugin page would be
>> I, for one, do not want any sort of "approval" process for plugins.
>> I'm unhappy with the theme approval process as it currently stands,
>> because I think it's horribly broken.
> I wholeheartedly agree.
>> Reviews are fine. User reviews would be excellent. But I just want to
>> be clear that we don't want to be putting anybody in the position to
>> deny plugins from being listed for not following some arbitrary set of
>> guidelines. That defeats the whole purpose of a code review, which is
>> to help the developer to learn better ways and to improve their code.
>> When you start denying listings because of not following some set of
>> practices, then you're creating a walled garden of content, which is
>> one reason I do not like the iTunes App Store and jailbroke my iPhone
>> within 3 days of getting it. I don't think the WordPress community
>> should try to emulate Apple in this case.
> you mean like the themes currently are? (sorry that may be seen as
> slightly offensive to the theme review team, it's aimed at the process
> rather than the reviewers).
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers