[wp-forums] Marking plug-ins as "broken."

[Peter Westwood]

On 29 Jul 2010, at 19:19, Eric Mann wrote:

> I am so frustrated with people who try to download my plug-ins, fail to read the
> included Readme file, install the plug-in incorrectly, then report it as
> "broken" without bothering to post a reason why.  One of my "flagship" plug-ins
> is now marked as "broken" with 3 votes, and I'm at a loss as to whether it
> really is broken or if it's a PEBCAK problem.
>  
> The latest forum post complaining about my plug-in demonstrates that the user
> failed to read the Readme file ... he was trying to pass too many parameters
> into a function and was receiving an error.  His assumption was that the system
> had broke because a feature he *thought* existed wasn't working ... but that
> feature was never there in the first place!
>  
> </rant>
>  
> What I'd really like to do is require some kind of feedback if you mark a
> plug-in as broken.  Somehow require the user to post an explanation and have
> that explanation seed a new forum thread so that developers can respond.
>  Otherwise, we're allowing people to say "this apple didn't taste like a
> cheeseburger, so it must be broken" and that feedback reflects poorly on
> developers ... there's no way to separate and respond to legitimate bug reports.
> 

I believe that this may come out of the ongoing 3.org projects

Cheers
-- 
Peter Westwood
http://blog.ftwr.co.uk | http://westi.wordpress.com
C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5