User talk:Jraber

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m
(Update)
Line 1: Line 1:
I am currently working to create some basic metrics to report on the activities on the [[BugZappers]]. My current approach employs the [https://fedorahosted.org/python-bugzilla/ python-bugzilla] package and a few basic Bugzilla queries.
+
I am currently working to create some basic metrics to report on the activities on the [[BugZappers]]. My approach is to use the [https://fedorahosted.org/python-bugzilla/ python-bugzilla] package as much as possible.
  
 
== Proposed Metrics ==
 
== Proposed Metrics ==
* '''# of Bugs 'Triaged' in the last xx days''' - See: [https://bugzilla.redhat.com/buglist.cgi?cmdtype=runnamed&namedcmd=BugsTriaged-Last30Day]
+
{|
* '''# of Bugs 'Triaged' in the last xx days by Current Status''' - Slightly modified bugzilla-python can create this report.
+
! Description !! Status !! Comments/Notes/Reference
* '''# 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 Bugs 'Triaged' in the last xx days || DONE || See: [https://bugzilla.redhat.com/buglist.cgi?cmdtype=runnamed&namedcmd=BugsTriaged-Last30Day]
* '''# 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.
+
|# of Bugs 'Triaged' in the last xx days by Current Status || DONE || bzilla query --from-url='https://bugzilla.redhat.com/buglist.cgi?chfieldto=Now&query_format=advanced&chfield=keywords&chfieldfrom=-90d&chfieldvalue=Triaged&classification=Fedora&product=Fedora' --summary bug_status
* '''List of 'Triaged' bugs currently marked as NEEDINFO''' - This should generally be an empty list.  Bugs being listed here could indicate poor Triaging. See: [https://bugzilla.redhat.com/buglist.cgi?type0-1-0=allwords&field0-1-0=flagtypes.name&field0-0-0=flagtypes.name&classification=Fedora&query_format=advanced&value0-1-0=Triaged&bug_status=NEW&bug_status=ASSIGNED&bug_status=MODIFIED&bug_status=ON_DEV&type0-0-0=allwords&value0-0-0=NEEDINFO&product=Fedora]  (**NEED TO TEST THIS**)
+
|-
* '''# of bugs CLOSED by BugZappers in last xx days'''
+
|# of Bugs 'Triaged' in the last xx days by Component || DONE || bzilla query --from-url='https://bugzilla.redhat.com/buglist.cgi?chfieldto=Now&query_format=advanced&chfield=keywords&chfieldfrom=-90d&chfieldvalue=Triaged&classification=Fedora&product=Fedora' --summary component
* '''# of bugs CLOSED by BugZappers in last xx days by BugZapper'''
+
|-
* '''# of bugs CLOSED by BugZappers in last xx days by Resolution'''
+
|# of Bugs 'Triaged' in the last xx days by Triager || In Process || 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.)
 
+
|-
== My Thoughts/Questions ==
+
|# of 'Triaged' bugs CLOSED in last xx Days || DONE || See: [https://bugzilla.redhat.com/buglist.cgi?keywords=Triaged&chfieldto=Now&query_format=advanced&chfield=bug_status&keywords_type=allwords&chfieldfrom=-90d&chfieldvalue=CLOSED&bug_status=CLOSED&classification=Fedora&product=Fedora]
* 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.
+
|-
 +
|# of 'Triaged' bugs CLOSED in last xx Days by Resolution || DONE || bzilla query --from-url='https://bugzilla.redhat.com/buglist.cgi?keywords=Triaged&chfieldto=Now&query_format=advanced&chfield=bug_status&keywords_type=allwords&chfieldfrom=-90d&chfieldvalue=CLOSED&bug_status=CLOSED&classification=Fedora&product=Fedora' --summary resolution
 +
|-
 +
|# of 'Triaged' bugs CLOSED in last xx Days by # of days since Triaged flag was set || PENDING || To know if/how 'Triaging' is impacting the life expectancy of bugs. (This metric needs to be defined better)
 +
|-
 +
|List of 'Triaged' bugs currently marked as NEEDINFO || PENDING || This should generally be an empty list.  Bugs showing up here could be an indicator of  poor Triaging. See: [https://bugzilla.redhat.com/buglist.cgi?type0-1-0=allwords&field0-1-0=flagtypes.name&field0-0-0=flagtypes.name&classification=Fedora&query_format=advanced&value0-1-0=Triaged&bug_status=NEW&bug_status=ASSIGNED&bug_status=MODIFIED&bug_status=ON_DEV&type0-0-0=allwords&value0-0-0=NEEDINFO&product=Fedora]  (**NEED TO TEST THIS**)
 +
|-
 +
|# of bugs CLOSED by BugZappers in last xx days || PENDING || Need a list of BugZappers
 +
|-
 +
|# of bugs CLOSED by BugZappers in last xx days by BugZapper|| PENDING ||Need a list of BugZappers
 +
|-
 +
|# of bugs CLOSED by BugZappers in last xx days by Resolution|| PENDING ||Need a list of BugZappers
 +
|}
 +
== Additional 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 'Triaged' 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.
 
* 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.
 
* Pretty graphs could be created showing how these metrics change (or don't) over time.
* What other great data points could we be tracking?
+
* What other metrics should we be tracking?
  
== Current Stats ==
+
== Current Metrics as of  June 22, 2010==
***Updated on Tuesday June 22, 2010
+
Bugs Triaged in the last 60 Days: 327
Triaged Bugs (last 60 Days): 327
+
  
 
   By Current Status:
 
   By Current Status:
 
 
       ASSIGNED - 60
 
       ASSIGNED - 60
 
       CLOSED - 65
 
       CLOSED - 65
Line 31: Line 43:
 
       ON_QA - 11
 
       ON_QA - 11
 
       VERIFIED - 2
 
       VERIFIED - 2
  By Component: (this could take a moment...)
 
  
 +
  By Component:
 
       NetworkManager - 1
 
       NetworkManager - 1
 
       PackageKit - 19
 
       PackageKit - 19

Revision as of 19:22, 28 June 2010

I am currently working to create some basic metrics to report on the activities on the BugZappers. My approach is to use the python-bugzilla package as much as possible.

Proposed Metrics

Description Status Comments/Notes/Reference
# of Bugs 'Triaged' in the last xx days DONE See: [1]
# of Bugs 'Triaged' in the last xx days by Current Status DONE bzilla query --from-url='https://bugzilla.redhat.com/buglist.cgi?chfieldto=Now&query_format=advanced&chfield=keywords&chfieldfrom=-90d&chfieldvalue=Triaged&classification=Fedora&product=Fedora' --summary bug_status
# of Bugs 'Triaged' in the last xx days by Component DONE bzilla query --from-url='https://bugzilla.redhat.com/buglist.cgi?chfieldto=Now&query_format=advanced&chfield=keywords&chfieldfrom=-90d&chfieldvalue=Triaged&classification=Fedora&product=Fedora' --summary component
# of Bugs 'Triaged' in the last xx days by Triager In Process 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 DONE See: [2]
# of 'Triaged' bugs CLOSED in last xx Days by Resolution DONE bzilla query --from-url='https://bugzilla.redhat.com/buglist.cgi?keywords=Triaged&chfieldto=Now&query_format=advanced&chfield=bug_status&keywords_type=allwords&chfieldfrom=-90d&chfieldvalue=CLOSED&bug_status=CLOSED&classification=Fedora&product=Fedora' --summary resolution
# of 'Triaged' bugs CLOSED in last xx Days by # of days since Triaged flag was set PENDING To know if/how 'Triaging' is impacting the life expectancy of bugs. (This metric needs to be defined better)
List of 'Triaged' bugs currently marked as NEEDINFO PENDING This should generally be an empty list. Bugs showing up here could be an indicator of poor Triaging. See: [3] (**NEED TO TEST THIS**)
# of bugs CLOSED by BugZappers in last xx days PENDING Need a list of BugZappers
# of bugs CLOSED by BugZappers in last xx days by BugZapper PENDING Need a list of BugZappers
# of bugs CLOSED by BugZappers in last xx days by Resolution PENDING Need a list of BugZappers

Additional 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 'Triaged' 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 metrics should we be tracking?

Current Metrics as of June 22, 2010

Bugs Triaged in the last 60 Days: 327

  By Current Status:
     ASSIGNED - 60
     CLOSED - 65
     MODIFIED - 5
     NEW - 184
     ON_QA - 11
     VERIFIED - 2
  By Component:
     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