Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.26.0

Request #10359 Developer bugfix stats for last month
Submitted: 2007-03-13 16:28 UTC Modified: 2007-04-11 22:16 UTC
From: timj Assigned: cellog
Status: Closed Package: pearweb (version 1.10.2)
PHP Version: Irrelevant OS:
Roadmaps: 1.13.0    
Subscription  


 [2007-03-13 16:28 UTC] timj (Tim Jackson)
Description: ------------ On http://pear.php.net/bugs/stats.php it would be nice to have a "most active bug-fixing developers" table for the last month (or something similar), to get a sense for who is active right now.

Comments

 [2007-03-30 00:39 UTC] mj (Martin Jansen)
I think we should be careful with regard to adding more "developer high scores" to the website. Monthly statistics usually do not reflect the overall involvement of people in PEAR accurately and thus shed a bad light on people who are normally pretty active but are unable to work on the project for a few weeks because of other constraints etc..
 [2007-03-31 10:26 UTC] timj (Tim Jackson)
What you're saying is true if you regard stuff like this as a kind of "scoring" mechanism or some reflection on merit. I don't, and I don't think that was the intention of the existing tool. If you regard it as merely a "curiosity" or an interesting aside (or maybe a useful tool to see who might be a good person to chat to informally about something based on how active they've been recently) then it doesn't *matter* whether someone has been busy or not. It's just a chart after all. That said, I suppose a statement on the page explicitly pointing out that being "high" or "low" on the chart doesn't actually mean anything and that nobody is being "rated" based on it, wouldn't hurt.
 [2007-04-11 22:16 UTC] cellog (Greg Beaver)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.