Task:Bugzilla report card - Revision history

qgil: Undo revision 8853 by qgil (Talk)

qgil — Thu, 20 Nov 2008 12:04:26 GMT

Undo revision 8853 by qgil (Talk)

← Older revision		Revision as of 12:04, 20 November 2008
Line 16:		Line 16:
	\|- style="background:LightBlue"		\|- style="background:LightBlue"
	\| Browser \|\| 23/34 \|\| 10/29 \|\| Good \|\| Good response rate, but fixes are slow.		\| Browser \|\| 23/34 \|\| 10/29 \|\| Good \|\| Good response rate, but fixes are slow.
-	~~\|- style="background:Orange"~~
-	~~\| Desktop \|\| 2/19 \|\| 12/15 \|\| Yellow \|\| Excellent fix rate, but communication is sorely lacking.~~
-	~~\|- style="background:Tomato"~~
-	~~\| Connectivity \|\| 5/25 \|\| 2/25 \|\| Poor \|\| Poor fix rate and poor communication leaves a lot to be desired.~~
-	~~\|- style="background:LightGreen"~~
-	~~\| Utilities [[Image:Star.png]] \|\| 10/10 \|\| 5/5 \|\| '''Excellent!''' \|\| Perfect response rate, perfect fix rate (excluding moreinfo bugs).~~
-	\|}
-
-	~~{\| class="wikitable sortable"~~
-	\|-
-	~~! Team !! January !! February !! March !! April~~
-	\|-
-	~~\| Browser \|\| style="background:LightBlue" \|\| 10/29 \|\| Good \|\| Good response rate, but fixes are slow.~~
	\|- style="background:Orange"		\|- style="background:Orange"
	\| Desktop \|\| 2/19 \|\| 12/15 \|\| Yellow \|\| Excellent fix rate, but communication is sorely lacking.		\| Desktop \|\| 2/19 \|\| 12/15 \|\| Yellow \|\| Excellent fix rate, but communication is sorely lacking.

qgil: /* Report format */

qgil — Thu, 20 Nov 2008 12:03:04 GMT

Report format

← Older revision		Revision as of 12:03, 20 November 2008
Line 16:		Line 16:
	\|- style="background:LightBlue"		\|- style="background:LightBlue"
	\| Browser \|\| 23/34 \|\| 10/29 \|\| Good \|\| Good response rate, but fixes are slow.		\| Browser \|\| 23/34 \|\| 10/29 \|\| Good \|\| Good response rate, but fixes are slow.
		+	\|- style="background:Orange"
		+	\| Desktop \|\| 2/19 \|\| 12/15 \|\| Yellow \|\| Excellent fix rate, but communication is sorely lacking.
		+	\|- style="background:Tomato"
		+	\| Connectivity \|\| 5/25 \|\| 2/25 \|\| Poor \|\| Poor fix rate and poor communication leaves a lot to be desired.
		+	\|- style="background:LightGreen"
		+	\| Utilities [[Image:Star.png]] \|\| 10/10 \|\| 5/5 \|\| '''Excellent!''' \|\| Perfect response rate, perfect fix rate (excluding moreinfo bugs).
		+	\|}
		+
		+	{\| class="wikitable sortable"
		+	\|-
		+	! Team !! January !! February !! March !! April
		+	\|-
		+	\| Browser \|\| style="background:LightBlue" \|\| 10/29 \|\| Good \|\| Good response rate, but fixes are slow.
	\|- style="background:Orange"		\|- style="background:Orange"
	\| Desktop \|\| 2/19 \|\| 12/15 \|\| Yellow \|\| Excellent fix rate, but communication is sorely lacking.		\| Desktop \|\| 2/19 \|\| 12/15 \|\| Yellow \|\| Excellent fix rate, but communication is sorely lacking.

generalantilles: New page: {{task|proposed}} {{quotation|Something that would help in the Fremantle timeline is to define what products (aka which teams) are doing better and worse. Now there is an overall complain...

generalantilles — Wed, 19 Nov 2008 08:59:01 GMT

New page: {{task|proposed}} {{quotation|Something that would help in the Fremantle timeline is to define what products (aka which teams) are doing better and worse. Now there is an overall complain...

New page

{{task|proposed}}

{{quotation|Something that would help in the Fremantle timeline is to define what products (aka which teams) are doing better and worse. Now there is an overall complaint, which is unfair to actually those individuals and teams that are doing a good work in bugs.maemo.org. The general complaint is also more difficult for us to chase reasons why things are how they are. If instead there would be a wiki page or something showing "red - yellow - green - star" status of each product matching a team, then we all would be able to focus on the right spots.|Quim Gil}}

== Metrics ==

Grading is based on response rate (how many incoming bugs were responded to?), fix rate (excluding moreinfo, DUPLICATE, WORKSFORME, and INVALID), and (Bugsquad?) perception based on experience with the team.

== Report format ==

'''NOTE: This table is entirely bogus.'''

{| class="wikitable sortable"
|-
! Team !! Response !! Fix !! Rating !! Comments
|- style="background:LightBlue"
| Browser || 23/34 || 10/29 || Good || Good response rate, but fixes are slow.
|- style="background:Orange"
| Desktop || 2/19 || 12/15 || Yellow || Excellent fix rate, but communication is sorely lacking.
|- style="background:Tomato"
| Connectivity || 5/25 || 2/25 || Poor || Poor fix rate and poor communication leaves a lot to be desired.
|- style="background:LightGreen"
| Utilities [[Image:Star.png]] || 10/10 || 5/5 || '''Excellent!''' || Perfect response rate, perfect fix rate (excluding moreinfo bugs).
|}

[[Category:Community]]
[[Category:maemo.org]]
[[Category:Bugzilla]]