Re: the bug stats on pearweb

Helgi Þormar wrote: > Hi guys, > > As many people know we now have bug stats pear developer, by month, overall > and such stuff but at the moment it only includes bugs and doc problems, > why > not rename it from bug stats into ticket stats and include feature requests > also ? > > Or should that be yet another column ? > > I'd think it would be neat to see that even tho it's not strictly bugs but > since those stats are mostly just ego boosts (we don't use those developer > stats for anything useful per say) then IMHO we should perhaps include and > even put this all on a new page (stats.php is getting kinda heavy IMHO :P) > > What say ye ? Hi Helgi, In my experience with PEAR, I have not seen any great difficulty with developers implementing new features. However, we had an unchanging bug count of about 500+ for almost a year (according to PEARGirl on IRC) before the bug stats were introduced. The bug statistics are designed to encourage bug fixing. There was a bit of grumbling about the sinister nature of statistics, but the proof is in the pudding: the bug count is down to 370 +/- 10, with the lowest snapshot count I've seen being about 365. We still have a ways to go (and most of the bugs are in the Spreadsheet_Excel_Writer package/Mail_MimeDecode/SOAP packages), but personally I would like to keep these simple and think of them in a "how does this help PEAR" kind of way. Once the PEAR Group identifies their priorities for where PEAR should go, the statistics could be modified to help encourage movement in specific areas, whether it is porting packages to PHP 5, documentation, or whatever, but from my end, the point of the bug count is not a popularity contest, but to encourage behavior that is beneficial to the entire community of developers - taking pride in fixing bugs :) Greg