User talk:Jraber

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Current Stats)
m
Line 21: Line 21:
 
== Current Stats ==
 
== Current Stats ==
 
***Updated on Tuesday June 22, 2010
 
***Updated on Tuesday June 22, 2010
Triaged Bugs (last XX Days): 327
+
Triaged Bugs (last 60 Days): 327
  
 
   By Current Status:
 
   By Current Status:

Revision as of 17:17, 22 June 2010

I am currently working to create some basic metrics to report on the activities on the BugZappers. My current approach employs the python-bugzilla package and a few basic Bugzilla queries.

Proposed Metrics

  • # of Bugs 'Triaged' in the last xx days - See: [1]
  • # of Bugs 'Triaged' in the last xx days by Current Status - Slightly modified bugzilla-python can create this report.
  • # of Bugs 'Triaged' in the last xx days by Triager - Requires modification to bugzilla-python to enable gathering of 'history' data from bugzilla via XMLRPC. (The ability to get History data via XMLRPC was intrduced in BugZilla 3.4 and is marked as EXPERIMENTAL.)
  • # of 'Triaged' bugs CLOSED in last xx Days
  • # of 'Triaged' bugs CLOSED in last xx Days by Resolution
  • # of 'Triaged' bugs CLOSED in last xx Days by # of days since Triaged flag was set - To know if/how 'Triaging' is impacting the life expectancy of bugs.
  • List of 'Triaged' bugs currently marked as NEEDINFO - This should generally be an empty list. Bugs being listed here could indicate poor Triaging. See: [2] (**NEED TO TEST THIS**)
  • # of bugs CLOSED by BugZappers in last xx days
  • # of bugs CLOSED by BugZappers in last xx days by BugZapper
  • # of bugs CLOSED by BugZappers in last xx days by Resolution

My Thoughts/Questions

  • Who are the BugZappers? Where is the list of members of the BugZappers? Proposed alternative is: BugZappers = BugZilla users that have made use of the 'Trigaed' flag in the previous xx days.
  • Eventually, these metrics should probably come from a SQL query. Pulling all this data via XMLRPC will be slow.
  • Pretty graphs could be created showing how these metrics change (or don't) over time.
  • What other great data points could we be tracking?

Current Stats

      • Updated on Tuesday June 22, 2010

Triaged Bugs (last 60 Days): 327

  By Current Status:
     ASSIGNED - 60
     CLOSED - 65
     MODIFIED - 5
     NEW - 184
     ON_QA - 11
     VERIFIED - 2
  By Component: (this could take a moment...)
     NetworkManager - 1
     PackageKit - 19
     amarok - 1
     anaconda - 1
     ant - 1
     banshee - 1
     cman - 1
     compiz - 5
     compiz-fusion - 1
     control-center - 1
     devhelp - 2
     digikam - 1
     distribution - 1
     epiphany - 1
     evince - 2
     evolution - 3
     fedora-bookmarks - 1
     firefox - 37
     gc - 1
     glob2 - 1
     gnome-desktop - 1
     gnome-panel - 1
     gnome-session - 1
     initscripts - 5
     iptables - 1
     java-1.6.0-openjdk - 1
     k3b - 1
     kde-plasma-networkmanagement - 2
     kdeaccessibility - 1
     kdebase - 1
     kdebase-workspace - 3
     kdegraphics - 1
     kdelibs - 1
     kdenetwork - 1
     kdepim - 3
     kernel - 6
     knetworkmanager - 2
     libX11 - 4
     libXfixes - 1
     libdrm - 1
     livecd-tools - 1
     mesa - 5
     nautilus - 3
     nspluginwrapper - 1
     phonon - 1
     pixman - 1
     preupgrade - 1
     quodlibet - 1
     releng - 1
     rgmanager - 1
     seamonkey - 6
     spectrum - 1
     strigi - 3
     sugar - 1
     system-config-display - 2
     system-config-users - 1
     system-setup-keyboard - 1
     thunderbird - 14
     xine-lib - 2
     xine-ui - 1
     xorg-x11-apps - 1
     xorg-x11-drv-ati - 29
     xorg-x11-drv-evdev - 2
     xorg-x11-drv-intel - 42
     xorg-x11-drv-nouveau - 32
     xorg-x11-drv-nv - 1
     xorg-x11-drv-radeonhd - 1
     xorg-x11-drv-sis - 1
     xorg-x11-drv-synaptics - 1
     xorg-x11-drv-v4l - 1
     xorg-x11-drv-vesa - 2
     xorg-x11-drv-vmmouse - 3
     xorg-x11-drv-wacom - 6
     xorg-x11-fonts - 2
     xorg-x11-server - 30
     xulrunner - 3
     yelp - 1
     yum - 1