Difference between revisions of "Get Involved/Quality/Brainstorming"

Jump to: navigation, search
m
Line 1: Line 1:
[[Category:Improve]]
+
[[Category:Testing]]
  
 
This temporary page is aimed at brainstorming.
 
This temporary page is aimed at brainstorming.
Line 8: Line 8:
  
 
= Beta Tester need special group in bugtracker =
 
= Beta Tester need special group in bugtracker =
 +
 
== Rational ==
 
== Rational ==
 +
 
Developers need to know that a bug has been created by a dedicated beta tester. Why is that important? If the developers know that the reporter is capable of producing high quality reports it is not needed to do the usual developer-user interaction but it can be assumed that the bug is valid.
 
Developers need to know that a bug has been created by a dedicated beta tester. Why is that important? If the developers know that the reporter is capable of producing high quality reports it is not needed to do the usual developer-user interaction but it can be assumed that the bug is valid.
 
--[[User:Mgraesslin|Mgraesslin]] 19:38, 5 April 2012 (BST)
 
--[[User:Mgraesslin|Mgraesslin]] 19:38, 5 April 2012 (BST)
  
 
= Personalized Thank You Letter =
 
= Personalized Thank You Letter =
 +
 
== Proposal ==
 
== Proposal ==
 +
 
Every user who reported e.g. ten high quality bug reports during the beta testing which got fixed before the release receive a personalized Thank You Letter signed by a prominent KDE developer.
 
Every user who reported e.g. ten high quality bug reports during the beta testing which got fixed before the release receive a personalized Thank You Letter signed by a prominent KDE developer.
 
--[[User:Mgraesslin|Mgraesslin]] 19:38, 5 April 2012 (BST)
 
--[[User:Mgraesslin|Mgraesslin]] 19:38, 5 April 2012 (BST)
  
 
= Competition For Best Bug Reporters =
 
= Competition For Best Bug Reporters =
 +
 
== Proposal ==
 
== Proposal ==
 +
 
The users who report most bugs during the beta test which get fixed before the release can win a prize. Of course the bug reports have to be of high quality.
 
The users who report most bugs during the beta test which get fixed before the release can win a prize. Of course the bug reports have to be of high quality.
 
--[[User:Mgraesslin|Mgraesslin]] 19:38, 5 April 2012 (BST)
 
--[[User:Mgraesslin|Mgraesslin]] 19:38, 5 April 2012 (BST)

Revision as of 13:28, 6 April 2012


This temporary page is aimed at brainstorming.

Please move things to be done to the collaborative tool here: https://trello.com/kdetesting

Ask Anne-Marie or Myriam for help if needed.

Beta Tester need special group in bugtracker

Rational

Developers need to know that a bug has been created by a dedicated beta tester. Why is that important? If the developers know that the reporter is capable of producing high quality reports it is not needed to do the usual developer-user interaction but it can be assumed that the bug is valid. --Mgraesslin 19:38, 5 April 2012 (BST)

Personalized Thank You Letter

Proposal

Every user who reported e.g. ten high quality bug reports during the beta testing which got fixed before the release receive a personalized Thank You Letter signed by a prominent KDE developer. --Mgraesslin 19:38, 5 April 2012 (BST)

Competition For Best Bug Reporters

Proposal

The users who report most bugs during the beta test which get fixed before the release can win a prize. Of course the bug reports have to be of high quality. --Mgraesslin 19:38, 5 April 2012 (BST)


Content is available under Creative Commons License SA 4.0 unless otherwise noted.