Apache OpenOffice (AOO) Bugzilla – Issue 7912
IZ stats per project
Last modified: 2003-02-10 10:23:03 UTC
Hi, Stefan As you recall, we discussed the feasibility and desirability of generating IZ reports per project, to evaluate, on a per project basis, the filing/resolution of IssueZilla tickets. This is b/c we urge community members to post patches via IZ; a tabulation of IZ activity will thus give us a better sense of overall contributions. Ideally, I'd like for this data to be routinely tallied and incorporated into the spreadsheet. I'd also like for it to be tabulated for the Oct 13 anniversary. thanks louis
see ongoing discussion...
reassigning to Joost.
reassigning
Created attachment 3684 [details] Proposed Format for IZ stats
Created attachment 3697 [details] OpenOffice.org issue statistic per project
Created attachment 3740 [details] IssueZilla bug count statistic for the week from 11/18/02 to 11/25/02
Joost: accepted issue as started
Created attachment 3834 [details] Parse Stats for All current projects.
ParseStats.pl is a first stab at an automated Perl based system for gathering of stats. First, HTTP::Lite is needed from CPAN. ActiveState PPM is a good source if you are stuck in Windows. ( I am too at the moment ;-( ) Currently, the script pulls down the full listing for each project and parses the Status field. NOTE: This is not exactly true, ;-). I cheated. What I do is parse out <nobr>UNCO</nobr>, <nobr>NEW</nobr>, etc... You can look in the script for the URL I am using. <replace> gets replaced for each project. An example of the output can be found in today.csv. The next step is to put the information into a database. I am thinking we can use Progbits and just have a Cron job fire at 12am. Put all the entries into a database with the date, and then we could provide a page to download the information to CSV. What do you think? A little long winded, eh. ;-) Forgive me, it's 12:44 am. My eyes are going buggy. I'll chat with you soon. P.S. Average time for the script is about a minute, to gather ALL stats for ALL projects. P.S.S. I have DSL. It still has to download the full page, but it only does it once per project.
Created attachment 3835 [details] Sample output from ParseStats.pl in CSV format
Joost->Scott: The output of ParseStats.pl is good. Would it be possible to get a column containing the current date ? It would make things easier to generate a changes history just by copying these csv files together plus generating subtotals.
Created attachment 3856 [details] IssueZilla bug count statistic for the week from 11/25/02 to 12/02/02
Created attachment 3982 [details] IssueZilla bug count statistic for the week from 12/02/02 to 12/09/02
Created attachment 4055 [details] IssueZilla bug count statistic for the week from 12/09/02 to 12/16/02
Shouldn't we publish the stats in the web area of the QA project? Export to html seems to work fine.
Created attachment 4102 [details] Updated file with date added.
out of curiosity, what do people say about my sending along the mailinglist stats to QA? or should we have a general stats page elsewhere? louis
I think we should post a Stats page on QA. This way you can go straight to the site to retrieve stats. Any ideas on format?
See my suggestion above: As a start why not take the attached files, convert them to html and commit them to the QA project web space (www/stats) directory. Greetings, Stefan.
Why not take the spreadsheet format? Or save it as html, looks good, too. By the way, I guess you can take the components "oi" and "scripting" out of the perl script. Both are not valid components in IZ anymore. I've just set the last oi issue to the now correct component, which is framework.
Created attachment 4216 [details] IssueZilla bug count statistic for the week from 12/16/02 to 01/06/03
Created attachment 4281 [details] IssueZilla bug count statistic for the week from 01/06/03 to 01/13/03
Joost: today I added the task statistic as html file to our project page. I will follow on updating this file until we have an automated version.
JA: I removed the components "oi" and "scripting" from the statistics page as Michael wanted it. I added a statistic for all open features and enhancements which have not yet been resolved. The new format will be visible next monday. After publishing these files I see no more reason to leave this issue open. JA->Gordon/Scott: perhaps someone of you could get this automated. I could post the latest calc file containing the URL's to you if there is any interest in this.
JA: posted new statistics page containing "open feature" issues
JA: closed this issue